confluence_get_blog_post_versions

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

No annotations, so description covers all key behaviors: pagination, default trimming, full parameter for raw response. Discloses response shaping.

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 efficient sentences, front-loaded with purpose. Every word adds value, 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 and response format trade-offs. Could specify what trimmed fields are, but adequate for a version list tool with no output schema.

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% (baseline 3). Description adds meaning for pagination (cursor), trimming (full), and bodyFormat (enum context). Not all parameters elaborated but key ones are.

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+resource: 'Get version history for a specific blog post.' Distinct from sibling tools like confluence_get_blog_post_version (singular) and confluence_get_page_versions (pages).

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?

Explains pagination with cursor and response trimming behavior. No explicit when-to-use vs alternatives, but context is clear for a retrieval tool.

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