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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds the consequential side effect that tracking begins immediately. It also explains the retry contract ('Pass a fresh requestId and reuse it if you retry'), which complements rather than contradicts idempotentHint=false.

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 persistent-tracking effect is front-loaded in the first clause, followed by the discovery pointer and the idempotency note. Three tight sentences with little waste, though the phrasing is dense and slightly clause-heavy.

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?

An output schema exists, so return values needn't be explained, and annotations carry the safety profile. The description covers the main behavioral surprise (immediate persistent tracking) and the retry semantics; it does not mention limits, billing or failure modes, but nothing essential to invoking 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 description coverage is only 17% (just requestId), so the description must compensate. It does add meaning for three params in prose ('website domains' and 'the names it is mentioned by', plus name), but organizationId and projectId are left entirely undescribed, so the gap is only partially filled.

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 gives a specific verb (Add) and resource (competitor to a project), then explains the persistent effect: its mentions and rankings are tracked alongside the brand's. This clearly separates it from update_competitor and delete_competitor, which only modify or remove an already-tracked competitor.

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?

It names an explicit discovery path ('list_untracked_competitors shows the brands AI answers name that are not tracked yet'), which tells the agent where to source candidates before calling this. It does not state exclusions (e.g. use update_competitor instead when the competitor already exists), so it falls just short of a full 5.

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