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

With no annotations, the description carries the burden. It discloses the exact output structure (verdict tally, feature table, strengths, best-for, FAQ, page URL) and a limitation ('Covers 60 competitors'). It does not state side effects, but for a read-only lookup tool, this is adequate transparency.

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 a single well-structured sentence that front-loads the main verb and resource, then uses a colon to list the output components. No filler words; every element adds value.

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?

Given the simple single-parameter input and no output schema, the description fully covers what the tool returns and its scope. It does not need to explain return values because it already lists every component of the response.

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% (the sole parameter 'competitor' has a description with examples). The tool description adds little beyond the schema, just calling it a 'named ERP or CRM competitor.' Since the schema already does the heavy lifting, the description adds no extra meaning, so the baseline 3 is appropriate.

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 uses a specific verb ('Return') and clearly identifies the resource ('head-to-head comparison of Odoo against a named ERP or CRM competitor'). It also enumerates the contents (verdict tally, feature table, strengths, best-for guidance, FAQ, URL), distinguishing it from sibling calculators and generic selection tools.

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 clearly contextualizes when to use the tool: when comparing Odoo to a specific named competitor. It also states the scope ('Covers 60 competitors'), implicitly indicating it is not for other competitors. However, it does not mention alternatives or explicitly say when not to use it.

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