confluence_label_remove

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

Discloses destructive nature and guard mechanism (confirm: true). No annotations to supplement, but description adequately flags behavioral traits. Lacks detail on error cases beyond confirm refusal.

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?

Three concise front-loaded sentences. Every sentence adds essential information with no filler.

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?

Simple tool with complete schema. Description covers guard and CLI equivalence. Lacks return value description but output schema absent; overall sufficient for agent invocation.

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%; description reinforces the critical confirm parameter with context beyond schema (destructive guard). Adds value without redundancy.

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?

Clearly states 'Remove one or more labels from a Confluence page'. Specific verb-resource pair. Context of destructive guard and CLI mirror further clarifies without overlapping sibling tools.

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?

Explicitly warns about destructive operation and required confirm flag. References a CLI command for familiarity. Does not explicitly state when to use instead of label_add/label_list, but sibling differentiation is implied.

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