decompose

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

Annotations already declare readOnlyHint true, destructiveHint false, idempotentHint true, openWorldHint true. The description adds deprecation context and redirect, which goes beyond annotations without contradiction.

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 line, extremely concise, and front-loaded with the key deprecation info. Every word is necessary, but it lacks parameter explanation.

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?

With 4 parameters, 0% schema coverage, no param descriptions, and no explanation of the tool's behavior (only deprecation), the description is incomplete for an agent that might need to use this tool. The output schema exists but doesn't compensate for the lack of input semantics.

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%, and the description provides no information about the four parameters (cohort_id, horizon, max_slices, explain) beyond the schema defaults and requirement. This is a critical gap.

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 the tool is deprecated and redirects to analyze(metric='decompose', cohort_id=...), which implies the original purpose was decomposition. It clearly communicates what the tool does in context of its deprecation.

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?

Explicitly states '[DEPRECATED in v5 — use analyze(metric="decompose", cohort_id=...)]', providing a clear when-to-use and when-not-to-use instruction with a direct alternative.

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