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

With no annotations, the description carries the full burden. It usefully discloses that the operation is idempotent and that future events stop, but it does not mention return behavior, error cases, permissions, or what happens if the watch does not exist.

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 compact sentence with no wasted words. It front-loads the core action, then adds the two most valuable behavioral facts: idempotency and the consequence that future events stop.

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?

For a simple two-parameter tool the description covers the core action and main behavioral effects, and the schema supplies the enum and constraints. However, with no annotations and no guidance on parameter semantics or usage context, it remains only minimally complete.

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 0%, so the description needed to compensate. It only restates the parameters as 'kind and target,' which adds little beyond the parameter names. It does not explain what targetId represents, how it relates to the watch enum, or what formats are expected.

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 opens with a specific verb and resource: 'Revoke a watch by kind and target.' This clearly distinguishes it from the sibling watch_* tools, which create watches, and from get_watches, which lists them.

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 use case is implied by the verb 'Revoke' and the sibling names watch_thread, watch_community, and watch_competition, but there is no explicit statement of when to use this tool versus those alternatives, nor any preconditions such as verifying that a watch exists.

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