confluence_get_blog_post_labels

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

No annotations are provided, so the description carries full burden. It discloses two key behavioral traits: pagination (use cursor) and response trimming (default drops fields, use full=true for raw). This is sufficient for a read operation, though it does not cover error handling or rate limits.

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 two sentences, concise and front-loaded. First sentence states purpose, second explains pagination and trimming. No redundancy or fluff.

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 output schema, the description covers purpose, pagination, and response trimming. It does not detail the format of labels, but the tool name implies the output structure. For a read tool with 5 parameters, this is adequately complete.

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%, so baseline is 3. The description adds value by contextualizing pagination (cursor) and trimming (full parameter), explaining what trimming drops (_links, _expandable, body content). This exceeds the schema's descriptions, which are already clear but benefit from this extra context.

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 tool gets labels on a specific blog post, using the verb 'get' and resource 'labels on a blog post'. It distinguishes from sibling tools like get_page_labels (different resource) and add/remove blog post label (different action). The purpose is unambiguous.

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 guides usage by specifying the resource and mentioning pagination and trimming behavior. It does not explicitly state when not to use or contrast with alternatives, but the context of sibling tools makes it clear that this tool is for reading labels, not modifying them, and for blog posts specifically.

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