Get Blog Post

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds that it is free and requires no API key, plus the content nature (AI synthesis). Adds value beyond annotations.

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 short paragraphs: first line states purpose, second adds usage context, then Args section. Front-loaded, no wasted words, every sentence earns 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?

Tool is simple with one param. Description covers purpose, param guidance, cost/auth, and content nature. Output schema exists (not shown) so return value explanation is unnecessary. Complete for a read operation.

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 describes slug as type string with no description. The description adds 'Article slug, taken from list_blog_posts results', giving provenance and usage guidance. With 0% schema coverage, this fully compensates.

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 explicitly states 'Get the full Markdown body of one published blog post by its slug', which is a specific verb+resource pair. It clearly distinguishes from siblings like list_blog_posts and get_opportunity.

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?

Provides clear context: 'Free; no API key required' and notes the content is an original AI synthesis. It implies the slug comes from list_blog_posts, guiding workflow. No explicit when-not-to-use, but sufficient for the task.

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