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

No annotations are provided, so the description carries the full behavioral burden, and it mostly repeats the confirm parameter's own schema text ("confirm-gated" vs. the schema's preview explanation). It says nothing about permission/role requirements, whether the update is a full replacement of name and address, or reversibility.

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 waste and the action stated first. For a mutation tool it is arguably too spare, keeping it just short of a 5.

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 mutation tool with no annotations, no output schema, and three required parameters at 25% coverage, the description is far too thin. It omits prerequisites, the id source, and any confirmation-flow detail the agent needs before calling.

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 25% (confirm only), but the phrase "rename or re-address" usefully maps onto the name and address parameters, partially compensating. locationId remains undocumented in both schema and description, so a 3 is the ceiling.

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 pair and resource ("Rename or re-address an existing location"), and "existing" signals it is distinct from create_organization_location/delete_organization_location. However it never names a sibling, so differentiation rests on inference rather than explicit routing.

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 when-to-use guidance beyond the parenthetical "(confirm-gated)". It does not tell the agent to look up a locationId via list_organization_locations first, nor contrast this with the broader update_organization tool. Usage is left entirely to inference.

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