conf_get_labels

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The only added context is the cryptic "(one page)"; the description says nothing about pagination continuation, rate limits, or what happens when start exceeds the result count.

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?

Four words with no wasted text, but the brevity comes at the cost of clarity; the parenthetical is under-specified rather than informative. Front-loading is fine, but there is essentially nothing to front-load.

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?

With no output schema, no parameter descriptions, and a read-open-world tool that returns paginated data, the agent has no way to know the response shape or how to detect and fetch further pages. The description does not fill any of these gaps.

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 description coverage is 0% for three parameters (pageId, start, limit), so the description must compensate. It only hints at paging with "one page" and never clarifies that pageId is the Confluence page whose labels are listed, nor how start/limit behave together (defaults 0/25, max 100).

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?

"List labels" names a verb and resource, but the parenthetical "(one page)" is ambiguous: it could mean pagination (one page of results) or labels belonging to one Confluence page. An agent can infer listing vs. the sibling conf_add_label, but cannot tell the scope precisely.

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?

There is no guidance on when to use this versus conf_add_label, conf_search, or conf_get_page. Usage is only implied by the verb "List", with no prerequisites or exclusions stated.

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