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

With no annotations, the description carries the full disclosure burden. It reveals a non-obvious side effect: every successful call writes one license_events row with event_type='compliance_report_generated' BEFORE returning. It also covers authentication requirements, window caps, pagination behavior, and output shape, which goes well beyond what the schema exposes.

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 dense but every sentence conveys a distinct, high-value fact: purpose, output shape, fan-out behavior, side effect, window cap, pagination strategy, legal framework mapping, and authentication. It is front-loaded with the core purpose. The only minor weakness is the jargon-heavy phrasing like 'Phase 11 M4' and 'procurement-defense', which adds little operational clarity.

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 tool with no annotations and no output schema, the description is unusually complete. It explains the response shape, row fan-out, compliance framework anchors, side effects, pagination pattern, and required credentials. An agent has enough context to select the tool, provide valid inputs, and interpret the results.

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 coverage is 100%, so baseline is 3. The description adds value by explaining how the cursor should be used (_meta.next_cursor), how the window cap affects calling strategy, and how annual audits should be broken into quarterly windows. These details enhance the parameter semantics beyond the schema entries.

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 states a specific verb and resource: 'Generate a procurement-defense compliance dossier via GET /buyer-compliance-report'. It also differentiates from the closest sibling by explicitly contrasting the 90-day window cap with get_audit_events' 30-day cap, so an agent can tell which tool is intended.

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 clear operational guidance: it states the 90-day per-call window, contrasts it with the sibling's 30-day cap, and instructs agents to paginate via _meta.next_cursor across four quarterly windows for annual audits. It does not explicitly list exclusions or say 'use X instead', but the usage context is strongly implied and actionable.

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