Get product pricing

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

Annotations already declare readOnlyHint=true, so the safe read nature is covered. The description adds valuable behavioral context: it returns only the 10 most recent changes and mentions the API key requirement for deeper history. It doesn't contradict annotations, and the extra detail about history depth is useful.

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 two sentences with no fluff. It packs purpose, usage, parameter guidance, and a limitation into a compact, front-loaded format. Every sentence earns its place.

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 tool with one parameter, a clear schema, and readOnly annotations, the description fully covers the tool's function, when to use it, how to get the slug, and its output limitation. No output schema is present, but the description conveys the result (pricing plans and recent changes) sufficiently. Nothing essential 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% with a clear description for the single 'slug' parameter ('Product slug, e.g. "notion"'). The description reinforces this by pointing to search_products for finding slugs, adding practical guidance beyond the schema. This exceeds the baseline for high coverage.

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 it retrieves a SaaS product's current pricing plans and recent price changes, distinguishing it from siblings like search_products (which finds products) and recent_price_changes (which may be a broader filter). The verb 'get' and specific resource 'product pricing' are precise.

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?

Explicitly states when to call: 'when the user asks what a specific product costs, what plans it offers, or whether its price changed recently.' Also instructs to find the slug via search_products, and notes the 10-change limit with an API key requirement for deeper history. This provides clear context and alternatives.

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