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

Annotations already declare readOnly/stateless/non-destructive, and the description partially repeats them, but it also adds a credential requirement ('requires X-RapidAPI-Key') that is not in the annotations or schema. It stops short of describing latency, output sizing, or any failure modes for oversized context input.

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?

Purpose is front-loaded, but the middle is one sprawling sentence with a long parenthetical list, and the safety traits are restated redundantly ('read-only, stateless, non-destructive'). The parameter character limits are repeated from the schema, adding bulk without new meaning.

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 complex generation tool, the definition covers input shape, auth, posture variations, and intended workflow, and an output schema exists so return values need not be spelled out. Nothing an agent needs to invoke it correctly is missing.

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% and already documents all three parameters, so the baseline is 3. The description adds genuine cross-parameter meaning by stating that `bidder_discriminators_and_proof_points` and `evaluation_type_and_posture` tailor the ghosting prose across Best-Value Tradeoff vs. LPTA, which is not evident from either field description alone.

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 and resource ('Conduct a Shipley Black-Hat competitive intelligence simulation on a target solicitation and incumbent contractor') and then enumerates the concrete deliverables (unseating probability, competitor profiles, ghosting statements, vulnerability matrix, Red Team triggers). An agent can distinguish it from every sibling without opening the 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 gives an explicit triggering condition ('when running a pre-RFP or pre-proposal Black-Hat competitive review') plus two named alternatives with the conditions that select them: match_capability_statement for a Gate-1 Bid/No-Bid Pwin score and generate_igce_price_to_win for LCAT/wrap-rate modeling.

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