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

With no annotations, the description carries the full burden. It thoroughly discloses the return structure including conditional fields like 'recipe (with nutrition + cuisine when applicable).' It does not mention errors or auth, but for a read-only fetch, the output detail is highly transparent.

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 sentences, both purposeful. The first sentence enumerates the rich return fields in a structured way, and the second provides direct usage guidance. No wasted words; front-loaded with the primary action.

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?

Given no output schema and no annotations, the description compensates by enumerating all returned fields, including nested structures and conditional elements. Combined with clear usage guidance and a well-documented single parameter, it is fully complete for the tool's purpose.

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 covers the single parameter with a clear description and example (100% coverage), so the baseline is 3. The description only repeats the concept of 'by slug' without adding extra meaning about the parameter itself.

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 begins with a specific verb+resource: 'Fetch the full machine-readable rendition of a tutorial by slug.' It clearly distinguishes from siblings by detailing the full content payload, and the phrase 'Use this after search_tutorials' sets it apart from search and listing tools.

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?

Explicitly states 'Use this after search_tutorials to fetch step details,' which provides clear when-to-use guidance and names the alternative tool. This effectively implies that search_tutorials is for discovery and this tool is for retrieval.

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