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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by explaining that output is deterministic, syntax-validated, and that mutating operations are disabled by default. This goes beyond the annotations without contradicting them.

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, well-structured sentence that front-loads the core action and includes only value-adding qualifiers. No redundant or filler words.

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?

The description provides a clear overview but is insufficiently detailed for an 8-parameter tool. It omits how parameters like auth environment variables, timeouts, and limits affect test generation. The output schema likely covers return values, but the description still leaves gaps in operational context.

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?

With 8 parameters and zero schema description coverage, the description should compensate but only indirectly references the 'document' parameter through 'caller-supplied OpenAPI 3 document.' The other parameters (format, base_url, api_key_env, bearer_token_env, etc.) are left undefined, and the schema titles/defaults do not fully clarify their semantics.

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 uses a specific verb ('Generate') and specifies the exact resource ('pytest and requests smoke tests') and source ('caller-supplied OpenAPI 3 document'). It also includes distinctive qualifiers ('deterministic, syntax-validated') and clearly distinguishes this tool from sibling tools like openapi-audit.

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 implies the use case: generating smoke tests from an OpenAPI document when deterministic, validated tests are needed. It does not explicitly mention alternatives or exclusions, but the context is clear enough given that sibling tools like openapi-audit serve a different purpose.

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