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

With no annotations, the description carries the full burden. It states the operation is a read ('Read the full text'), which implies non-mutating behavior, but it doesn't disclose what happens for missing slugs, output format, or any other side effects. This is adequate for a simple read tool but lacks richer behavioral detail.

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 that directly states the action, resource, and how to get the required input. Every word earns its place with no filler or redundancy.

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 tool with one parameter, a clear schema, and no output schema, the description is complete. It tells the user what the tool does and how to obtain the required slug, covering the essential aspects for successful invocation.

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 100% with a clear example for slug. The description adds value beyond the schema by telling the user where to obtain the slug (list_posts or search_posts), which clarifies the expected parameter value and usage context.

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 reads the full text of a Radixia blog post by slug, using a specific verb ('Read') and resource ('blog post') with a precise identifier method ('by its slug'). It also distinguishes itself from siblings by referencing list_posts and search_posts for slug retrieval.

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 gives clear context on how to obtain the required slug ('get the slug from list_posts or search_posts'), which implies the prerequisite workflow. It doesn't explicitly state when not to use this tool, but the guidance is clear enough for selecting this over sibling tools.

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