clusters

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

Annotations already declare readOnly, not destructive, and idempotent. The description adds crucial behavioral context: the tool is deprecated and will be removed, which warns agents against relying on it long-term.

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 extremely concise—just one sentence—and front-loads the deprecation warning. For a deprecated tool, brevity is acceptable, though it omits parameter details.

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 tool is deprecated, the description adequately tells agents to use an alternative. However, it does not explain the tool's original purpose or parameter meanings, which might be needed if an agent must still invoke it for backward compatibility.

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?

Input schema has 3 parameters with 0% description coverage. The description does not explain any of the parameters (cohort_id, horizon, k) or their semantics, leaving an agent without guidance on correct invocation.

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 indicates deprecation and points to an alternative ('use analyze'), which implicitly suggests the tool performs clustering. However, it does not explicitly state the tool's basic function, leaving some ambiguity for an agent unfamiliar with the alternative.

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 explicitly states that this tool is deprecated in v5 and provides the exact alternative call using 'analyze' with specific parameters, giving clear guidance on when to avoid this tool and what to use instead.

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