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

The readOnlyHint annotation already covers safety, so the description does not need to repeat that. It adds a behavioral note that includeUsageCounts is 'slightly slower' and clarifies that project scope returns groups of structurally identical schemas, which goes beyond the annotation.

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 two sentences, well-structured, and directly addresses the core behavior and the key variation (project scope). Every clause adds relevant information without redundancy or fluff.

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?

Given the lack of an output schema, the description covers the essential operational context: what the tool lists, the optional usage counts, the special project-scope behavior, and the requirement for project context. It does not detail the output structure, but that is reasonable since no output schema is provided.

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 input schema already describes all four parameters, so the baseline is high. The description enriches this by explaining the interaction between scope and specId (specId is ignored in project scope) and by noting the performance implication of includeUsageCounts, adding value beyond the schema.

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 the tool's function with a specific verb ('List') and resource ('all schemas of an API specification'). It also differentiates the project scope behavior, helping distinguish it from related siblings like get_schema or list_shared_schemas.

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?

The description gives some usage context, such as setting scope to 'project' for cross-spec analysis and noting that specId is ignored in that mode. However, it does not explicitly mention when to use this tool versus alternative tools or name alternatives, leaving some ambiguity about selection.

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