add_card

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

Discloses that the card is due immediately and returns JSON with card_id and due. Covers scheduling and first review. No annotations provided, but description adequately conveys behavioral traits for a creation tool.

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 sentences, front-loaded with purpose, no wasted words. Efficiently covers all essential information.

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?

Complete for a simple creation tool. Covers purpose, parameters, return value, and scheduling. Output schema is present, so return details are handled. No gaps given the tool's 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 has 0% description coverage, but the description explains front as prompt/question, back as answer, and deck as group with default. Adds significant meaning beyond schema types.

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 verb 'Author' and resource 'flashcard', and mentions scheduling. Distinguishes from sibling tools like delete_card, edit_card, grade_card, etc. by focusing on creation.

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 clear context for when to use (creating a new card) and explains optional 'deck' parameter with default. Lacks explicit when-not or alternatives, but the purpose is distinct from siblings.

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