List Labels

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

Beyond the readOnlyHint and destructiveHint annotations, the description adds behavioral details such as pagination via cursor, a default limit of 25 and maximum of 250, and accepted label_prefix values. This enriches the agent's understanding of how the tool behaves without contradicting annotations.

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 compact, front-loaded with a one-sentence summary, and then uses a clean Args list. No redundant or filler content is present.

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 simple read-only list tool with four optional parameters and no output schema, the description provides sufficient context: purpose, scope, parameter semantics, and pagination behavior. Minor gaps remain around the exact return format and the meaning of 'body representation,' but these are not critical given the tool's simplicity.

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?

The schema has zero description coverage, and the description fully compensates by explaining all four parameters in the Args block: label_prefix, body_format, cursor, and limit, including allowed values and defaults. This adds substantial semantic meaning 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 clearly states it lists labels across the entire Confluence instance, using the specific verb 'list' and resource 'labels' with an explicit scope. This distinguishes it from sibling tools like list_page_labels and list_space_labels, which operate on narrower scopes.

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 gives clear context that this is an instance-wide label listing, implying it should be used for global label queries rather than page or space-specific ones. However, it does not explicitly name alternative tools or provide when-not-to-use guidance, so it stops short of full differentiation.

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