confluence_get_blog_post_attachments

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

With no annotations, the description fully discloses pagination and output trimming behavior (drops _links, _expandable, body). It explains the 'full' parameter to bypass trimming. While it does not mention authentication or rate limits, for a read operation, these details are adequate.

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. No wasted words: the first sentence states the action, the second covers pagination and trimming. Conciseness is optimal.

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 6 parameters, no output schema, and no annotations, the description covers purpose, pagination, and trimming. However, it lacks detail on the return structure (beyond noting dropped fields) and does not describe the full response format. A minor gap, but overall fairly complete for a list tool.

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 baseline is 3. The description adds value by explaining the cursor parameter for pagination and the 'full' parameter for raw response. Other parameters (blogPostId, limit, filename, mediaType) are already described adequately in the schema, so the description meaningfully supplements two parameters.

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 states 'Get attachments on a specific blog post,' clearly specifying the verb and resource. It distinguishes from sibling 'confluence_get_page_attachments' by targeting blog posts rather than pages, providing unique purpose clarity.

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 handling ('use the returned cursor') and trimming behavior, but does not explicitly state when to use this tool over alternatives like 'confluence_get_page_attachments' or mention prerequisites or exclusions. Usage context is clear but lacking explicit guidance on alternatives.

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