confluence_get_blog_post_version

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

With no annotations provided, the description carries full burden for behavioral disclosure. It clearly states that output is trimmed by default and what is dropped (_links, _expandable, body content), and explains the full parameter to bypass trimming. This is good transparency for a read operation, though it does not discuss authorization or rate limits.

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, both front-loaded with the purpose and key behavioral details. Every sentence adds value with no redundancy or filler.

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?

The description covers the trimming behavior but lacks details about the return structure (e.g., what fields are present in the trimmed output vs raw) and does not mention response size limits or pagination. Given no output schema, more detail would be helpful for completeness.

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 the input schema already documents all parameters. The description adds meaning beyond the schema by explaining the effect of the 'full' boolean parameter and the default trimming behavior, providing context that helps the agent decide. The other parameters (blogPostId, versionNumber) are standard and need no further explanation.

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 ('Get a specific version of a blog post') and the resource. It is distinct from listing versions or retrieving the current post, though it does not explicitly differentiate from sibling tools like confluence_get_blog_post or confluence_get_blog_post_versions.

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 the default trimming behavior and the full parameter, guiding when to use each. However, it does not provide explicit when-to-use or when-not-to-use advice relative to other version-related tools (e.g., confluence_get_blog_post_versions for listing, or confluence_get_blog_post for the current version), leaving usage context implied.

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