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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that the output is plain-text full body, but it does not mention missing-post behavior, locale defaults, or any notable side effects.

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 a single, front-loaded sentence with no redundant filler. Every word contributes to the core behavior, making it highly efficient.

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?

For a simple get-by-slug operation, the core input and output are stated, but the description omits guidance on not-found behavior and the relationship to sibling search tools. With no output schema, those gaps are not filled elsewhere.

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 description coverage is 50%; locale is fully explained in the schema, while slug has no schema description. The tool description confirms slug is the lookup key but adds no detail about slug format or how locale affects the returned content beyond what the schema already says.

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 identifies the resource (blog post), the lookup key (slug), and the return type (full plain-text content), making the purpose clear. It lacks an explicit verb, but the tool name and 'by slug' make retrieval unambiguous. It only implicitly differentiates from siblings like search_blog_posts.

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?

There is no guidance about when to use get_blog_post instead of search_blog_posts or other content tools. The description simply states the lookup mechanism, leaving the agent to infer that this tool is for fetching by a known slug.

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