get_tool_guide

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

No annotations provided, so the description carries the full burden. It describes the content (examples, anti-patterns, etc.) and available tools but does not explicitly state it is read-only or has no side effects. However, the tone and purpose strongly imply it is a harmless guide retrieval.

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 efficient sentences with a parenthetical list. No wasted words—every sentence earns its place. The key action and prerequisites are front-loaded.

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 one-parameter tool with no output schema, the description fully covers purpose, content, usage timing, and available options. No gaps remain for an AI agent to resolve.

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 coverage is 100% (parameter tool_name has a description listing valid values). The main description reinforces these values, adding contextual meaning (e.g., 'or "all" for a summary'). This adds value beyond the schema's bare enumeration.

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 'Get usage guide for a rendering tool' and specifies it includes examples, anti-patterns, complexity limits, and tips. It differentiates from sibling rendering tools by being a guide retrieval rather than a rendering action.

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 advises 'Call this BEFORE your first render to avoid common mistakes,' providing clear when-to-use guidance. Also lists available tool names, helping the agent choose the correct parameter value.

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