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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context by detailing return values (median spend, category breakdown, savings %) and citing data source (Stratalize PE Intelligence composite), enhancing transparency beyond the annotations.

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?

Three focused sentences: use case, return values, and an illustrative example. No redundant or filler content. The structure is efficient and front-loaded with the most important usage information.

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?

The description provides return value details and an example, which is helpful given no output schema. However, the complete omission of parameter semantics is a significant gap, as the agent cannot determine how to invoke the tool with meaningful arguments. This balances to a minimum viable score.

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?

The input schema has two parameters (sector and company_count), but the description does not mention either. With 0% schema description coverage, the description entirely fails to explain what these parameters do, acceptable values, or how they affect results. This is a severe gap.

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 benchmarks PE portfolio company technology spend, specifying use case and return metrics. It distinguishes from sibling tools that focus on categories or industries by emphasizing 'portco' and 'across a portfolio'.

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 explicitly says 'Use when benchmarking portco technology spend for PE operating partners or building a software cost reduction case across a portfolio', providing clear when-to-use context. However, it does not mention exclusions or alternatives, so it stops short of full guidance.

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