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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the mutation profile is partly covered. The description adds an auth prerequisite ('Requires API key'), which is genuinely useful context beyond the annotations, but it fails to disclose that the tool can delete keywords via 'remove', a behavior an agent would want flagged given destructiveHint=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?

Two short sentences with the core operation front-loaded and zero filler. Size is appropriate for a simple three-parameter tool.

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 need not be explained, and the schema documents all parameters. Still, the description omits the 'remove' action entirely and provides no routing guidance against 13 sibling tools, leaving meaningful gaps for a multi-action 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 description coverage is 100%, so the schema already documents 'action', 'keyword' and 'targetUrl' including which are required for which action (baseline 3). The description adds no parameter meaning beyond listing the add/list behaviors, and it never mentions 'targetUrl' or the remove path.

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 (track) and resource (keywords for a site), so the agent knows it manages tracked keyword data. However, the description says 'Add or list' while the schema's action enum also includes 'remove' — the purpose statement undercounts what the tool does, and it doesn't distinguish itself from siblings like get_opportunities.

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?

No guidance on when to use this versus sibling tools; the only constraint offered is 'Requires API key'. There is no mention of when-not-to-use or which alternative handles related keyword work.

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