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

Annotations only declare destructiveHint: false, which is minimal. The description adds the behavioral detail that links/elements follow because screens are id-referenced, shedding light on side effects. However, it doesn't cover prerequisites, reversibility, or possible collisions beyond the schema's note.

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?

A single, front-loaded sentence that uses emphasis (caps) to convey key nuances. It is concise and every phrase adds meaning, though could be slightly more structured with a trailing note.

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 rename tool with no output schema, the description explains the critical behavioral outcome (links follow) but omits context about project_id disambiguation and how success is indicated. It's adequate for a straightforward tool but not rich.

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?

The description adds no parameter information. Schema coverage is 67%, with descriptions for 'name' and 'new_name', but 'project_id' is undefined. The description's 'id-referenced' clue is too indirect to clarify parameter usage or the role of project_id.

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 uses a specific verb ('Rename') and resource ('screen'), and adds clarity by specifying 'IN PLACE' and 'DIRECT', distinguishing it from proposal-based workflows. It also clarifies the effect on links/elements, making the purpose unambiguous.

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 phrase 'IN PLACE — DIRECT' implies this is the actual rename action rather than a proposal, but it does not explicitly name alternatives (like propose_screen) or state when not to use it. The description gives context but lacks explicit exclusions.

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