The Prompt Decorators MCP server has 7 tools covering decorator discovery, application, and validation. Tool naming is generally good (verb-first pattern: list_, get_, apply_, validate_, search_), and descriptions are present for all tools and parameters. However, there are significant gaps in schema completeness and parameter documentation. Most tools have descriptions in the 40-100 character range, which is brief but adequate. Input schemas are visible in the code and include type information (string, object, array), but lack detailed constraints (enums, min/max values, patterns). Parameter descriptions are minimal and don't always explain the expected format or valid ranges. Output schemas are not documented, critical for LLMs to understand what fields to expect from results. Error handling and recovery guidance are absent from all tool definitions. The server operates on READ_ONLY operations (no destructive actions), which reduces security risk but also means no idempotency, confirmation, or permission-gate patterns are tested.

• Document the output schema for every tool. Include field names, types, and what they represent. Example: 'Returns array of objects: [{name: string, description: string, category: string, parameters: object}]'
• Add explicit constraints to parameters. For apply_decorator, specify valid parameter keys or provide examples. For validate_decorator_syntax, explain the expected syntax format. For get_decorators_by_category, list or link to the valid category enum.
• Expand parameter descriptions to 50-100 characters. Include format hints: 'The search query (1-256 chars, supports wildcards)' instead of just 'Search query to find matching decorators.'
• Add error handling guidance to tool descriptions. Example: 'If the decorator is not found, call list_decorators to see available options. If the syntax is invalid, call validate_decorator_syntax to diagnose the error.'
• If list_decorators or search_decorators return many results, add limit and offset parameters with documented defaults (e.g., limit=20, offset=0) and return a total_count field for pagination.
• Document whether apply_decorator is idempotent (safe to retry) and whether apply_multiple_decorators processes all decorators or stops on first error.
• Consider adding a get_decorator_categories tool to help users discover valid categories for get_decorators_by_category, or include the full category list in the description.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry