confluence_get_pages_for_label

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

The description discloses that the response is trimmed by default and that passing 'full=true' returns the raw Confluence response. It also mentions pagination with a cursor. This adds transparency beyond the input schema descriptions, especially since no annotations are provided.

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, each serving a clear purpose: the first states the main function, the second explains pagination and output options. No extraneous information.

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 the tool's 6 parameters and no output schema, the description covers the core behaviors: pagination and response trimming. It is sufficient for a read operation but could mention ordering or edge cases. It is complete enough for effective 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?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining the context of the 'full' parameter (trimming behavior) and the pagination mechanism ('cursor'), which is not fully captured in the 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 starts with 'Get all pages with a specific label,' which is a specific verb and resource. It clearly distinguishes from siblings like 'confluence_get_pages' (no label filter) and 'confluence_get_pages_in_space' (filter by space).

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 explains pagination ('use the returned cursor to fetch more pages') and the trimming behavior, which helps the agent decide how to use the tool. However, it does not explicitly contrast with alternatives or state when not to use it.

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