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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds valuable context: it never assigns a grade, does not treat startup credits/deals as service readiness, and returns precise missing fields when the service graph is incomplete. These behavioral traits go beyond the annotations and help an agent set expectations.

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 dense paragraph with an overlong list of assessment aspects ('vendor product, API, SaaS service, authentication path, payment path, provisioning flow, operating interface, recovery flow, and exact agent standard'). While it communicates purpose, it could be tightened and front-loaded with the key behavior (YAML generation) before the exhaustive enumeration.

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?

Despite the extreme complexity of the input schema (16 parameters, 11 required, nested objects, enums), the description offers no guidance on how to construct a valid request, what the required fields represent, or any example. The absence of parameter semantics makes it nearly impossible for an agent to call this tool correctly without external knowledge.

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?

Schema description coverage is 0%, and the description provides zero explanation of the 16 parameters or their meaning. Required fields such as command_contract, scope_source_uris, assessment_targets, and others are completely unexplained. The description focuses solely on the tool's output and constraints, leaving the agent to guess how to populate complex nested structures.

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: to prepare canonical GitHub-ready YAML for an Agent Readiness assessment. It enumerates the specific scope (vendor product, API, SaaS service, authentication path, etc.) and explicitly differentiates from grading or credit handling, making its purpose unambiguous.

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 does not mention when to use this tool versus alternatives, nor does it name any sibling tools or conditions for selection. It implies a niche use (readiness declarations) but offers no explicit guidance on when to prefer it over compare_offers, inspect_evidence, etc.

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