narrative_alerts

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

Discloses deprecation, a key behavioral trait not covered by annotations. Annotations already declare read-only and idempotent nature, so description adds value with versioning context.

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?

Extremely concise, front-loading the critical deprecation warning. While short, it serves its purpose without superfluous text.

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 deprecated tool, the description sufficiently informs agents to avoid it and provides the alternative. However, it lacks any functional detail for cases where the tool might still be used.

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 has 0% description coverage, and the description does not mention any parameters or their meanings. The agent must rely solely on parameter names and defaults.

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 only indicates deprecation and suggests an alternative tool. It does not explicitly state the tool's purpose or behavior, leaving the agent to infer from the name and alternative syntax.

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?

Clearly states not to use this tool in v5 and provides the exact alternative, giving explicit when-not-to-use and replacement guidance.

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