Recent SaaS price changes

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds valuable context: 'fixed snapshot of up to 25 entries per group—no pagination' and 'verified' data, informing the agent about result limits and data quality. No contradiction with 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?

Two sentences cover purpose, usage triggers, and constraints with no redundancy. The main action is stated first, followed by usage guidance.

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 parameterless tool with readOnlyHint, the description fully explains what it returns (recent changes, biggest movers), the time frame (30 days), scope (whole catalogue), and the limitation (up to 25 per group, no pagination). This is sufficient for an agent to decide when to use it.

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?

There are zero parameters, so schema coverage is 100%. The baseline for zero-param tools is 4; no parameter-specific descriptions are needed.

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 provides recent verified SaaS price changes and biggest movers over 30 days, and it distinguishes itself from sibling tools (search_products, get_product, compare_products) which have different purposes.

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 specifies when to use: 'Call this when the user asks what changed in SaaS pricing lately, who raised prices recently, or for examples of price increases.' Also notes the fixed snapshot and lack of pagination so the agent knows not to expect more results.

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