modify_hierarchical_label

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

Annotations indicate destructiveHint=true, which aligns with modification, but the description does not add behavioral context beyond parameter purposes. It fails to disclose side effects like immediate application or required write access.

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 compact bullet list with no extraneous text. Each sentence provides necessary information without redundancy.

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 7 parameters, 1 required, and an existing output schema, the description covers parameter semantics well. However, it lacks context about error conditions or the need for the label to exist, which is minor.

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?

Each parameter is explained with its role and default behavior (e.g., 'empty = keep current', 'None = keep current'). This adds significant meaning beyond the schema, especially with 0% schema coverage.

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 starts with 'Modify an existing hierarchical label', which is a specific verb+resource combination. It clearly distinguishes from sibling tools like add_hierarchical_label, remove_hierarchical_label, and modify_hierarchical_sheet.

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 implicitly suggests use for modifying labels but does not explicitly state when to use this tool versus alternatives (e.g., add or remove). No prerequisites or conditions are mentioned.

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