benchmark_sales

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

Annotations declare readOnlyHint, idempotentHint, destructiveHint false. Description adds behavioral detail such as ignoring hosting/aggregation and explains the meaning of *Percentile and *BenchmarkAllPartners fields, enhancing transparency.

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?

Starts with a summary, then output structure, then filtering notes, then spec link. Some redundancy in output example, but overall efficient and well-structured.

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?

Despite no output schema, the description exhaustively documents the return shape and key metrics. Includes filtering behavior and a link to the full API spec, making it self-contained for agent invocation.

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 each parameter has a description. Description adds that addon and productId are alternatives but does not provide additional semantic value beyond the schema's own descriptions.

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?

Clearly states it returns 'Sales benchmark vs. ecosystem, per month' and details the output structure with fields like salesPercentile and salesMoMGrowth. Distinguishes from siblings like benchmark_evaluations by specifying sales focus.

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?

Specifies filtering by addon or productId and notes that hosting/aggregation are ignored. Provides a spec link for full context but lacks explicit guidance on when to use this vs other benchmark tools like metrics_churn_benchmark.

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