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

Annotations already flag destructiveHint=true, but the description adds crucial nuance: history is kept by default so past data remains readable, and records are only erased when delete_history is explicitly true. It also discloses the cost ('Free, costs no credits'), which is valuable behavioral context beyond the annotations.

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?

Three tight sentences with zero filler: the core action is front-loaded, followed by scope, the destructive default, and the cost note. Every sentence earns its place and nothing is repeated from the schema or annotations.

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?

The description covers purpose, scope, destructive caveat, and cost, and an output schema exists so return values needn't be explained. The main gap is the undocumented required target parameter plus no explicit sibling routing, but for a simple 3-param tool the definition is otherwise sufficient.

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?

With 0% schema description coverage, the description must carry parameter meaning. It explains that an empty keywords array stops the whole domain and that delete_history=true permanently removes records, but it never describes the required target parameter, leaving one of three parameters undocumented.

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 states a specific verb and resource: 'Stops daily automatic re-measurement for tracked keywords,' with scope control via the empty keywords parameter. It references seo_rank_history but does not explicitly differentiate itself from the start-tracking sibling (seo_rank_tracker), keeping it short of a 5.

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 gives clear operational context: use this to stop recurring measurement, leave keywords empty for the whole domain, and only set delete_history true when records should be permanently removed. However, it does not explicitly name alternatives such as seo_rank_tracker or describe when not to use this tool, so it lacks exclusion guidance.

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