confluence_get_page_labels

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

With no annotations, the description must disclose behaviors. It explains pagination via cursor, default response trimming (drops _links, _expandable, body), and the full option for raw response. This adequately informs the agent of the tool's key operational traits.

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 concise sentences that first state the purpose, then detail pagination and output options. No superfluous information; all sentences are informative and front-loaded.

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 get operation with no output schema, the description covers purpose, pagination, and output format (trimmed vs raw). Missing details on error handling or prefix format, but overall sufficient for an agent to use.

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 the baseline is 3. The description does not add significant new meaning beyond the schema's parameter descriptions; it reinforces pagination behavior but does not explain parameter formats or defaults beyond what schema provides.

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 retrieves labels on a specific page, using the verb 'get' and specific resource 'labels on a specific page'. This distinguishes it from sibling tools like add_label or remove_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?

Description mentions pagination and the full parameter, implying usage for large result sets or raw output. However, it does not explicitly state when to use this tool versus alternatives like getting page labels via other endpoints or comparing with other label tools.

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