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

The annotations already declare readOnlyHint=false and destructiveHint=true, but the description adds almost no behavioral context. It does not explain that updates may be destructive, whether omitted fields are preserved, or what happens when renaming an existing location.

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?

The description is a single front-loaded sentence with little waste. 'Rename or update' is slightly redundant because rename is a type of update, but the structure is efficient.

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 mutation with four parameters, 0% schema description coverage, and no output schema, the description is far too sparse. It should at least indicate which attributes can be changed and whether unspecified fields are left unchanged.

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 0%, so the description must carry parameter meaning, but it only vaguely implies that 'name' is updated via 'rename.' It provides no semantics for notes, address, or location_id and does not clarify that location_id is required.

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 states a clear verb and resource: 'Rename or update an inventory location.' It is distinguishable from create/delete siblings by the update verb, but it does not explicitly differentiate itself from create_stock_location, delete_stock_location, or list_stock_locations.

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 guidance on when to use this tool versus create_stock_location, delete_stock_location, or list_stock_locations. It also omits prerequisites such as whether the location must exist or whether the organization scope is implicit.

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