buddy-mcp

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

No annotations provided, so description carries full burden. Specifies output format (SVG) and scope (ASCII sprite only), but omits file system behavior details like overwrite behavior, return values, or side effects. The schema covers 'output file path', mitigating some transparency needs.

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?

Single 9-word sentence with zero waste. Front-loaded with action verb, immediately specifies scope ('just the sprite'), and identifies format. Every word earns its place.

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?

Appropriately complete for a simple single-purpose export tool with 100% schema coverage. No output schema exists (typical for file export tools). Could benefit from noting file-write behavior, but adequate given low complexity.

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% (path parameter fully documented with default value pattern). Description adds no parameter-specific details, but baseline 3 is appropriate since schema completely covers the single parameter.

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?

Specific verb 'Export' plus resource 'buddy ASCII sprite' and format 'SVG image file'. The word 'just' effectively distinguishes this from sibling 'export_buddy_card', indicating this produces only the visual sprite rather than a full card.

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?

Implies differentiation from 'export_buddy_card' through the word 'just', suggesting when to use this (sprite-only needs vs full card). However, lacks explicit 'when to use' guidance or named alternatives.

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