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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: it does not explain why a mere rename is flagged destructive, whether the old title is lost, or any auth/permission requirement.

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 short sentence with the verb front-loaded and zero filler. It is appropriately sized, though its brevity is partly why other dimensions are under-served.

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 destructive, non-idempotent mutation with no output schema and only 33% parameter documentation, the description omits usage guidance, parameter roles, and behavioral consequences. It leaves too much for the agent to infer before making an irreversible change.

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 coverage is only 33% (only interviewId is documented) and the description supplies no parameter meaning at all. It does not clarify that orgId scopes the organization, interviewId selects the interview, or title is the new name (and its 1-160 length constraint), so it fails to compensate for the coverage 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 gives a specific verb ('Rename') but the resource phrasing ('organization landscape Clarity capture') does not cleanly match the tool name ('Clarity Organization Interview') or its sibling family, and it silently narrows 'Update' to a rename only. An agent can roughly tell what it does, but the terminology drift between name, title, and description muddies the target resource.

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?

There is no statement of when to use this tool versus getClarityOrganizationInterview, listClarityOrganizationInterviews, finalizeClarityOrganizationInterview, or the parallel landscape/team interview update tools. No prerequisites or context are given, leaving routing entirely to inference from the name.

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