validate_response_models

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description carries the full burden. The description states the tool 'detects' issues, implying a read-only analysis, but does not disclose whether files are modified, what the output format is, or whether any side effects occur. Given the presence of an output schema, some behavioral disclosure is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence with no filler. It front-loads the action and target, making it immediately scannable. This is appropriately concise for a tool with a single parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a validation tool with one parameter and no annotations, the description is thin. It does not explain what the tool returns (despite an output schema), how it detects missing declarations, or any limitations. While the simplicity of the tool reduces the need for extensive detail, the lack of behavioral and parameter context makes it incomplete for an agent to use confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage and only one parameter, 'file'. The description adds no extra meaning about the parameter—its type, purpose, or expected format are entirely undocumented. The description fails to compensate for the schema's lack of detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action ('Detect') applied to a specific resource ('FastAPI routes') with a precise outcome ('missing a response_model declaration'). This distinguishes it from sibling tools like list_routes or detect_schema_orm_mismatches, which serve different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no mention of contexts where this validation is appropriate, nor any exclusions or prerequisites. The agent is left to infer usage from the name and description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.