spellbook_find_combos

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

Annotations (readOnlyHint, idempotentHint, openWorldHint) already indicate safe, idempotent, open-world behavior. Description adds context about filtering by color identity and returning up to limit combos with cards and results, which is informative beyond annotations.

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?

Description is three sentences, front-loaded with the main purpose, followed by optional filter and output summary. No unnecessary words, well-structured.

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?

Given no output schema and 3 parameters, the description covers the essential: search purpose, optional filter, and output nature. It could be more specific about the return format (e.g., list of combos), but it is adequate for the 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 coverage is 100% with parameter descriptions. Description adds value by providing examples for color_identity (e.g., 'sultai', 'BUG', 'wubrg') and clarifying the output structure (cards involved and results produced).

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?

Description clearly states the tool searches for known combos involving a specific card, with optional color identity filter and output description. Differentiates from sibling tools like spellbook_combo_details and spellbook_find_decklist_combos by focusing on combos involving a 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?

Description clearly indicates when to use this tool (search for combos by card), but does not explicitly exclude alternatives or mention when not to use it. Sibling tool names suggest specific use cases, but the description could be more explicit about differentiation.

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