confluence_get_blog_post

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

Description contains an internal contradiction: 'includes body content' but 'drops... body content' in trimmed output. No other behavioral traits disclosed (e.g., authentication, side effects). With no annotations, the description should provide full transparency but fails.

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 are concise, but the contradiction reduces clarity. It is appropriately structured but under-specifies important details.

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 8 parameters and no annotations or output schema, the description is insufficient. It does not resolve the contradiction, nor does it explain the purpose of other parameters beyond the schema. Usage guidance and behavioral context are missing.

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 100% of parameters with descriptions. The description adds one detail (full=true for raw response) already in schema, but no further semantic enhancement for other 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 clearly states the tool retrieves a specific blog post by ID, which differentiates it from sibling tools like get_blog_posts (plural) and other blog post operations. The verb 'Get' and resource 'blog post by ID' are unambiguous.

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?

No explicit guidance on when to use this tool vs alternatives (e.g., get_blog_posts_in_space, get_blog_post_versions). The description does not mention exclusions or prerequisites.

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