Get Blogpost

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful context about body_format and version retrieval but does not describe return structure or potential errors, so it provides moderate additional transparency.

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 very concise, using a clear Args list with no filler. Every sentence or line adds meaningful information, and the format is easy to scan.

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 core behavior of retrieving a blog post by ID is fully specified, and parameter nuances are documented. However, with no output schema, the description would benefit from stating the return type (e.g., the blog post object), leaving a minor completeness gap.

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 0%, but the description fully compensates by explaining the meaning of all three parameters. It defines blogpost_id as the ID, lists valid body_format values, and clarifies version as a historical version number, adding valuable semantics beyond the schema's bare types.

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 uses the specific action 'Get' with the resource 'blog post by ID', clearly distinguishing it from sibling tools like list_blogposts or create_blogpost. The purpose is immediately obvious and 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?

The description clearly implies usage for retrieving a single blog post by its ID, which provides clear context. However, it does not explicitly mention when to prefer it over alternatives like list_blogposts or get_page, so it does not earn the top score.

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