delete_hierarchy

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. 'Delete' implies a destructive operation, but the description does not mention irreversibility, cascading effects, permissions required, or what happens if the hierarchy is referenced elsewhere. It lacks important behavioral context for a mutation tool.

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 concise sentence that is easy to read and front-loaded with the key verb. However, it is too sparse to fully cover the tool's behavior and parameters, so the conciseness comes at the cost of completeness. It is appropriate only for a very simple, obvious operation.

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?

Given no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It does not explain the effect, return value, or prerequisites. While the operation concept is simple, the lack of any supplementary context makes the tool hard to invoke confidently for an agent.

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?

The input schema has 3 required parameters with no descriptions, and the description provides no additional meaning. It clarifies that the operation is 'from a table,' hinting at the 'table' parameter, but the 'hierarchy' and 'sessionId' parameters remain unexplained. With 0% schema description coverage, the description does not compensate.

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 action: 'Delete a hierarchy from a table.' It identifies the resource (hierarchy) and its scope (within a table). It is mostly specific but does not explicitly distinguish itself from sibling tools like remove_hierarchy_level, which could cause confusion about whether it deletes an entire hierarchy or a level within one.

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 alternatives such as remove_hierarchy_level or set_hierarchy_properties. The description provides no context about prerequisites, side effects, or situations where this tool is appropriate. It is a bare statement with no usage direction.

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