buddy-mcp

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

Zero annotations provided, yet description offers minimal behavioral disclosure. 'Mystery wheel' implies randomness but fails to clarify if this is destructive (deletes old buddy), transactional, reversible, or what data format is returned.

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 sentence, appropriately compact. Front-loaded with action verb. Slight deduction for cutesy 'mystery wheel' metaphor that could be more direct.

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?

Adequate for a simple-action tool but incomplete given the mutation nature implied by 'reroll'. Missing output description (no output schema present) and persistence guarantees.

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?

Zero parameters present in schema, establishing baseline of 4. Description correctly implies no user input is required for the randomization.

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?

Uses specific verb 'Spin' (metaphorically) and resource 'buddy identity' to indicate random generation/assignment. Clear what the tool does for itself, though 'mystery wheel' abstraction slightly obscures the mechanism.

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?

Provides no guidance on when to use this versus siblings like view_buddy_dex or export_buddy_card. No mention of prerequisites, costs, or consequences of rerolling.

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