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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description largely restates that ('read-only, stateless, non-destructive'), which earns no credit. It does add genuinely useful non-annotation context: an X-RapidAPI-Key is required and the two required string inputs have character bounds. However, it says nothing about latency, whether output is a generated document vs. inline text, or failure modes — notable given the tool's complexity.

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?

It is front-loaded with the core action and output artifacts before the constraints and alternatives, and every clause carries information. It is dense — the opening sentence stacks a long enumeration of deliverables — but no sentence is filler.

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?

An output schema exists so return values need no explanation, yet the description still enumerates deliverables, states the auth requirement, gives input size bounds, and routes to alternatives. For a complex, high-stakes compliance generator, an agent has everything needed to call it correctly.

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 100% and both enum parameters are documented in the schema, so the baseline is 3. The description's parameter-related content (character limits, SIN lists, catalog contents) duplicates the schema rather than adding new semantics for submission_type or pricing_disclosure_pathway beyond what the enums already convey.

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 opens with a specific verb (Map) over concrete resources (labor rate cards, SKUs, discounting practices, past projects) and names the exact output artifacts (SIN matrix, PPT ceiling rate card with 0.75% IFF gross-up, PRC guardrails, SCP-FSS-001 narrative). It explicitly distinguishes itself from generate_igce_price_to_win and match_key_personnel, so an agent can route without opening a schema.

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?

It states the triggering scenarios directly (GSA MAS eOffer, SIN addition eMod, GSAR 552.238-81 PRC/MFC audit) and names two alternative tools with the conditions that select them. Nothing about when-to-use or when-not-to-use is left to inference.

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