remove_hierarchical_label

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

Annotations already declare destructiveHint=true, so the destructive nature is covered. The description adds useful context about default schematic_path and UUID disambiguation, but does not disclose what happens on lookup failure or whether the file is modified, though output schema may cover return behavior.

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 efficient: a single-sentence purpose followed by a minimal bulleted list for parameters. Every line adds value, no redundancy or unnecessary detail.

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 single-object removal tool with annotations and an output schema, the description is largely complete. It covers target identification and optional path handling. Minor gaps like error behavior when not found are acceptable given existing structured data.

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 descriptions are absent (0% coverage), so the description carries the full burden. It provides clear definitions for text, schematic_path (including default behavior), and uuid (including disambiguation purpose), adding meaningful guidance beyond the raw schema.

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 specific verb ('Remove') and resource ('hierarchical label'), and differentiates from siblings like remove_label by specifying 'hierarchical'. It also clarifies matching by name or UUID.

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 implies usage for hierarchical labels and explains how to specify the target, but does not explicitly distinguish from alternatives like remove_label or mention when not to use it. The context of sibling tools and the name make the primary use case clear.

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