remove_hierarchy_level

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

With no annotations provided, the description carries the full burden. It discloses two important behaviors: remaining levels are renumbered densely, and the last level cannot be removed. This goes beyond the obvious 'remove' semantics. It doesn't mention permissions or reversibility, but for a removal operation, the disclosed behaviors are key.

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, dense sentence that front-loads the core purpose ('Remove a level from a hierarchy') and packs in crucial behavioral details without any fluff. Every clause earns its place.

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 simple mutation tool with no output schema and no annotations, the description covers purpose, key side effects, error condition, and an alternative tool. It doesn't mention return values, but that's not critical for a remove operation. It adequately addresses the main contextual gaps.

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 50%, with descriptions for 'level' and 'hierarchy' but not for 'sessionId' and 'table'. The description adds context to 'level' by explaining the renumbering and refusal behavior, but it doesn't clarify the role of sessionId or table. It provides some value beyond the schema's tautological 'the level to remove', but doesn't fully compensate for the missing parameter docs.

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 clearly states the action: 'Remove a level from a hierarchy' with a specific verb and resource. It also distinguishes from the sibling tool delete_hierarchy by noting the refusal to remove the last level and pointing to the alternative.

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?

The description explicitly says when not to use this tool: 'Refuses to remove the LAST level - a hierarchy cannot be empty; use delete_hierarchy instead.' This provides a clear exclusion and names the alternative tool for that case.

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