confluence_get_page_attachments

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

Discloses pagination (cursor mechanism) and response trimming. No annotations exist, so description carries burden well. Does not cover error cases or rate limits, but adequate for a read operation.

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 sentences, front-loaded with purpose, then pagination, then trimming. No 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?

Covers pagination, trimming, and filtering options. No output schema, so lacks return structure details, but sufficient for a list tool. Could mention required pageId and initial call (no cursor needed).

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 covers all 6 params (coverage 100%). Description adds meaning: explains cursor usage for pagination and full parameter for raw output, beyond schema descriptions.

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?

Clear verb 'get' plus specific resource 'attachments on a specific page'. Distinguishes from sibling get_attachment (single) and get_blog_post_attachments (different resource).

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?

Describes pagination and trimming behavior, gives parameter hint for full response. No explicit comparison to alternatives, but context is clear for typical use.

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