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

The annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful context about the output being escaped and self-contained HTML, and notes it spends no model credits, which is beyond the annotations. However, it doesn't discuss validation failure behavior or other edge cases.

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 extremely concise and front-loaded with the primary action, followed by a key cost note. Every sentence earns its place with no filler.

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 two parameters (one nested object), no output schema, and strong annotations, the description covers the core function and output format but leaves gaps around theme semantics, validation specifics, and any prerequisites. It is adequate but not fully complete for an agent to invoke confidently without further information.

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?

With 0% schema description coverage, the description needed to compensate for parameter documentation. It mentions the document is an rgf/0-draft document, which gives some context for the 'document' parameter, but it doesn't explain the 'theme' parameter at all, nor what the document object should contain. The enum values in the schema are self-explanatory only if the agent already knows what the themes look like.

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 validates and renders an rgf/0-draft document as HTML, using specific verbs and the output format. However, it doesn't explicitly distinguish from sibling tools like convert_recipe or parse_recipe, though the render-to-HTML action is distinct enough.

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 should be used when you need to validate and render an rgf/0-draft document to HTML, but it doesn't provide explicit guidance on when to use this tool versus alternatives such as convert_recipe or parse_recipe. No exclusions or when-not-to-use criteria are provided.

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