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

With no annotations, the description carries the behavioral burden and discloses important traits: required permission (owner or office, needs see_prices), the default 365-day window, treatment of undated prices as stale, and exclusion of archived items. It does not explicitly state read-only behavior or pagination, but the core behavioral context is present.

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?

The description is three tight sentences, front-loading the core condition and then adding the default and edge cases. Every sentence contributes useful information without repetition.

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 simple two-parameter list tool with an output schema, the description covers the key behavioral details: permission, default window, undated-price handling, and archived-item exclusion. Minor gaps like ordering or pagination are not critical given the output schema.

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 50%, and the description adds meaning for older_than_days by explaining the default window and override behavior. However, shop_id is undocumented in both schema and description, so the description only partially compensates for the coverage 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 states a specific resource and condition: price book items whose current price was set longer ago than the shop's stale window. It is clear what the tool returns, but it does not explicitly differentiate itself from siblings like pricebook_list or pricebook_priceHistory.

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?

Usage is implied by the stale-price condition and the permission note, but the description does not explicitly say when to use this tool instead of pricebook_list or pricebook_priceHistory. It gives enough context to infer the use case but leaves alternative selection to the agent.

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