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

No annotations exist, so the description carries full burden. It discloses output structure (change_type, severity, etc.) and mentions 'real detection date.' Since the tool is read-only, no mutation warnings needed. The description is transparent about what the tool returns, though it doesn't cover rate limits or authentication, which is acceptable given typical MCP conventions.

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 zero waste. It packs purpose, output details, parameter guidance, and differentiation into a concise, front-loaded structure.

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?

Without an output schema, the description adequately covers return value structure and parameter behavior. It lacks details on pagination or ordering, but for a data retrieval tool with a limit parameter, the information is sufficient for an agent to use the tool correctly.

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%, so baseline is 3. The description adds value beyond the schema by explaining the 'competitor' parameter's effect (scoping vs. market-wide) and clarifying defaults for 'since' (90 days) and 'limit' (20 max). This practical usage context justifies a score of 4.

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 returns 'structured pricing/packaging changes' from IndustryLens, listing specific fields (change_type, severity, materiality score, summary, detection date). It distinguishes itself from sibling tools by claiming uniqueness: 'No other public source exposes structured competitor pricing-diffs like this.'

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 provides explicit usage guidance: 'Pass a competitor to scope to one company, or omit it for a market-wide feed.' It also implies defaults (90 days) and limits. While it doesn't explicitly state when not to use or list alternatives, the context with sibling tools helps differentiation.

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