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

Goes well beyond the annotations: rename propagates because orders/sessions/reports store the id and look up the name, the id is preserved, and only the name is mutable. The one soft spot is calling renaming 'safe' while annotations carry destructiveHint=true — the description means referentially safe, but an agent may read 'safe' as low-risk, so the risk framing could be sharper.

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?

Front-loaded with the action, then layered with rationale and constraints. Every sentence carries information, though the doubled emphasis in 'the ONLY thing the cabinet lets anyone change... and the only thing this tool changes' is slightly redundant.

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 2-parameter mutation with no output schema, the description covers the prerequisite, side effects, and scope limits well. It does not say what a successful rename returns, which is the only remaining gap an agent might want filled.

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 100% and already documents both fields, including 'Station id from get_stations — not a name.' The description only restates the id source, adding no format, validation, or naming-constraint detail beyond the schema, so the baseline 3 applies.

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?

Opens with a precise verb+resource+scope: 'Rename one station.' It further delimits the tool by stating the name is the ONLY field it changes, which cleanly separates it from hub_create_station, hub_delete_station and hub_get_stations without opening any schema.

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?

Explicit when-to-use ('rename one station'), explicit prerequisite routing ('Takes the station id from get_stations'), and an explicit when-not with an alternative path: moving a till to another store means creating a new station there and deleting this one. That is the full when/when-not/alternative triad.

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