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

Annotations already convey read-only and non-destructive behavior. The description adds genuinely useful context: the Salesforce example, the source ('Stratalize procurement intelligence composite'), and the $0.10 USDC cost per call. It does not discuss data coverage, latency, or failure behavior, so it is not a 5.

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?

Four compact sentences, each earning its place: trigger, output list, concrete example, and source/cost. The use case is front-loaded, and the pricing is disclosed rather than hidden.

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 one-parameter read-only lookup with no output schema, this is complete: it tells the agent when to use it, what input is expected, what to expect back, the data source, and the cost. Nothing else is required 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?

With zero schema description coverage on vendor_name, the description compensates by showing the expected kind of value ('Salesforce') and stating 'for any vendor', which clarifies that vendor_name is a vendor name. It does not explicitly define the parameter or required format, but for a single simple string parameter this is adequate.

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 concrete trigger ('Use when preparing to renew or renegotiate a SaaS contract') and names the exact returned artifacts: discount percentage, negotiation windows, leverage points, auto-renewal risk flags, and a negotiation script. This makes the tool's job unmistakable against generic vendor benchmark siblings.

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 clearly states when to invoke: when renewing or renegotiating a SaaS contract. However, it does not explicitly name alternatives or exclusions, such as when to prefer get_saas_negotiation_playbook or get_vendor_contract_intelligence, so it misses the top of the scale.

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