get_blog_post

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It states that the tool reads 'complete details' but does not describe return format, error handling, authentication, or special behaviors. For a simple read operation this is adequate but lacks depth.

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?

One short sentence with no filler, front-loaded with the main verb and object. Efficient and to the point, with every word earning its place.

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 tool is simple, but the description does not place it among siblings or specify return values. Since there is no output schema, the description could have clarified that it returns full post details and when to prefer this over list_blog_posts. Missing guidance on use cases makes it moderately complete.

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?

The schema provides two string parameters with no descriptions (0% coverage). The description adds meaning by explaining they can be used interchangeably ('ID o slug') as lookup identifiers, which the schema does not convey. However, it does not clarify requiredness, format, or priority.

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 verb 'Obtiene' (gets) targeting 'detalles completos de un artículo de blog' and specifies lookup by ID or slug. This clearly distinguishes it from sibling tools like list_blog_posts and publish_blog_post.

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 implies the tool is for fetching a single blog post but does not explicitly state when to use it over list_blog_posts or publish_blog_post. No alternatives or exclusions are mentioned, leaving the usage context implicit.

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