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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: credential-free access and that data is rendered from the product page via proxied browser renderers, hinting at provenance and possible latency. It stops short of stating rate limits or failure modes, so not a 5.

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?

Front-loads what is returned, then provenance, then the parameter, then the alternative tool – a sensible order with no filler. The product_id explanation is verbatim-duplicated from the schema, which is minor redundancy but not bloat.

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 single-parameter read tool with an output schema and safety annotations already in place, the description covers purpose, field list, data source, parameter format, and the sibling alternative. Nothing an agent needs in order to call it correctly 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% and the schema already documents product_id with the identical '/p/{id}/{slug}/' example phrasing. The description adds a URL-pattern anchor but no meaning beyond what the schema supplies, so the baseline 3 applies.

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?

States a specific verb and resource ('Returns a normalized Capterra product profile') and enumerates the returned fields (name, description, category, aggregate rating). It also names the sibling it is not ('Use capterra_search to search Capterra products'), so an agent can separate this lookup from search without opening either schema.

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 routes the agent to capterra_search for the search use case, leaving retrieval-by-id as this tool's role. It doesn't add explicit exclusions or prerequisites beyond that, but the search-vs-fetch distinction is clear.

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