Anki MCP Server

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

With no annotations provided, the description carries full burden but only states it updates fields without disclosing behavioral traits like permissions needed, whether updates are reversible, rate limits, or error handling. It mentions adding audio as an example but doesn't explain broader implications or 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?

The description is concise with two sentences that are front-loaded with the core purpose. The second sentence adds context without redundancy, though it could be slightly more structured (e.g., separating usage examples).

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 annotations and no output schema, the description is incomplete for a mutation tool with 3 parameters. It lacks details on behavioral aspects, error cases, and what the tool returns, leaving gaps for an AI agent to understand full usage.

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%, so the schema already documents all parameters. The description adds minimal value by hinting at usage ('adding audio') and implying 'fields' is a dictionary, but doesn't provide additional semantics beyond what the schema specifies (e.g., format details for audio).

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?

The description clearly states the action ('Update specific fields') and resource ('an existing note'), distinguishing it from creation tools like 'create_note' and bulk operations like 'update_notes_bulk'. However, it doesn't explicitly differentiate from all siblings (e.g., 'generate_and_save_audio' might also modify notes).

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?

The description provides implied context with 'Perfect for adding audio or other content to existing cards', suggesting use cases, but lacks explicit guidance on when to choose this over alternatives like 'update_notes_bulk' for multiple notes or 'create_note' for new notes. No exclusions or prerequisites are mentioned.

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