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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), yet the description adds material context beyond them: credential-free public data, proxied browser rendering as the data source, and the key quirk that Capterra returns a fallback product list even for no-match queries. That last point pre-empts a false bug report and is exactly the behavioral disclosure an agent needs.

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-loaded with the return contract, then the rendering note and the no-match quirk, all of which earn their place. The trailing 'Use capterra_product to get a Capterra product' is slightly circular and reads as an afterthought, keeping it short of a 5.

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?

With an output schema present, the description needn't explain return values, and it appropriately focuses on sourcing and the fallback-results caveat. It is nearly complete for a one-param search tool, though it omits any hint on result limits or pagination.

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 description coverage is 100% for the single parameter, so the schema already documents 'q' fully. The description's 'q: Search query, e.g. slack' merely restates the schema field and adds no format or constraint detail, so the baseline of 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 ('Returns') and resource ('Capterra search-result products') and enumerates the returned fields (id, name, url, description, rating). It names the sibling capterra_product, letting an agent distinguish the search-list tool from the product-detail tool 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?

Points explicitly to capterra_product as the tool for retrieving a specific product, which gives an alternative. However, it does not state when a search is preferred over other Capterra siblings (e.g. capterra_reviews) or any exclusions beyond that single pointer.

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