confluence_attachment_list

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

Discloses pagination behavior (one page per call, cursor-based) and default limit. It does not disclose rate limits, error handling, or authentication requirements, but for a simple list operation this is adequate. No annotations are provided to contradict.

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?

Three sentences: first sentence gives purpose, second explains pagination, third mentions equivalent CLI command. No wasted words, all information 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?

Covers key aspects: what it does, pagination, default limit. It does not describe the return format (e.g., list of attachment objects) but mentions 'next_cursor', implying paginated response. For a simple list tool, this is nearly complete.

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 description adds context beyond the schema by explaining the pagination pattern and that only one page is returned per call. Schema descriptions already cover each parameter, but the description enhances understanding of how they interact.

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 action 'List attachments' and the resource 'on a Confluence page', and distinguishes from sibling tools like delete and upload. It also specifies that it only retrieves one page per call, which is precise.

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?

Provides clear instructions on pagination (using cursor) and default limit. However, it does not explicitly state when to use this tool versus alternatives (e.g., confluence_attachment_delete), nor does it mention 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.