confluence_add_blog_post_label

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

The description discloses output trimming behavior and the 'full' parameter to bypass it. However, with no annotations, it should also mention side effects like idempotency or authorization, which are omitted.

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?

Two sentences, front-loaded with purpose, no extraneous words. Every sentence adds value.

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?

Adequate for a simple label-add tool, but lacks explanation of default output format (after trimming) and error scenarios. Still reasonably complete given no output schema.

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% but the description adds value by explaining the 'full' parameter's effect and noting the default prefix. This enriches the schema beyond basic descriptions.

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 ('Add a label to a blog post') with a specific verb and resource. It distinguishes from sibling tools like 'confluence_add_page_label' and 'confluence_remove_blog_post_label'.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., adding labels to pages or spaces). The description focuses on behavior but lacks context for tool selection among similar siblings.

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