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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the geographic domain, the entity restriction to legal entities, and the fields returned (certificate status, products, certifier, location codes, source links), though it says nothing about result caps or pagination.

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 compact sentences with no filler; the scope, certifications and returned fields are front-loaded before the short legal-entity caveat. Dense but every clause carries information.

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 no output schema and six optional parameters, the description does cover the nature of the returned data, which compensates partly. However, it omits guidance on how the parameters combine (e.g. scheme vs q), any default for limit, and result-set behavior, leaving gaps for a six-parameter tool.

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 67%, so several parameters (scheme, product, geo) are documented in the schema itself. The description references 'products', 'certifier' and 'location codes' in passing but adds no syntax, accepted values, or defaults beyond what the schema already provides, 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 (Finds) and resource (companies and cooperatives holding certifications), narrows the domain to Central America, and enumerates the certification schemes and returned fields. It is clear what the tool does, though it never names a sibling to distinguish itself from tools like find_suppliers or search_places.

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?

There is no when-to-use or when-not-to-use guidance and no alternative is named. The only usage-shaped statement is the scoping constraint 'Legal entities only', which is a filter rather than a selection rule.

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