render_slides

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

No annotations provided, so description carries full burden. Discloses key behaviors: self-contained output, navigation, transitions, and content density limits (max bullets, code lines, quote words, total slides). Does not cover error handling or idempotency, but provides useful constraints.

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?

Three sentences front-loaded with purpose and key features. No redundant words. Efficiently conveys essential information, with a call to action for additional details.

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?

Covers purpose, constraints, and references external guide. Lacks details on output format (though implied) and error handling for limit violations. Given no output schema and 4 parameters, description is adequate but could be more thorough on edge cases.

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%, baseline 3. Description adds value by explaining that 'slides' is a JSON array string with specific structure and optional type, and includes content density limits per slide type, which go beyond the schema description.

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?

Clearly states the tool renders a self-contained HTML slide deck with specific features (keyboard navigation, progress bar). The verb 'render' and resource 'slide deck' are explicit. Distinguishes from sibling tools like render_mermaid and render_chart by focusing on slides.

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?

Mentions 'No Docker required' as a contextual note, suggesting alternatives might require Docker. Directs users to call get_tool_guide('slides') for more info, but does not explicitly state when to avoid this tool or compare directly with siblings.

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