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

With no annotations, the description carries the full behavioral burden for a mutation. It discloses only that the call is confirm-gated, which the schema already states in the confirm parameter description. It says nothing about required permissions, whether the rename is reversible, uniqueness constraints on names, or what the preview response contains.

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 with no wasted words. It is efficient, though for a mutation tool with three parameters it verges on under-specification rather than optimal brevity.

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-in-effect rename with no annotations, no output schema, and two undocumented parameters, the description leaves substantial gaps: who may call it, what the preview returns, and how to identify the target organization. It is not adequate on its own for safe invocation.

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 only 33% (only confirm is documented). The description implies the name parameter ('rename') and the confirm gate, covering two of three parameters, but adds no format, constraint, or lookup guidance for organizationId beyond what the bare minLength schema field shows.

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?

States a specific verb+resource: 'Rename an organization'. The choice of 'rename' rather than generic 'update' usefully distinguishes it from the sibling update_organization_profile, which presumably handles other fields. It stops short of naming that sibling explicitly, so it's clear but not fully differentiated.

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?

No guidance on when to use this instead of update_organization_profile or update_organization_custom_role, and no prerequisites such as required role (owner/admin). The only usage-adjacent signal is '(confirm-gated)', which is about mechanics rather than selection.

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