Anki MCP Server

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

With no annotations provided, the description carries the full burden and does well by disclosing key behavioral traits: it's a write operation (implied by 'Create'), handles duplicates gracefully with reporting, and includes important implementation details about the auto_audio parameter structure. It doesn't cover permissions, rate limits, or error handling, but provides substantial operational context.

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 appropriately sized but not optimally structured: the first paragraph is well-focused, but the auto_audio instructions dominate with repetitive warnings and an example that could be more concise. Some information (like the dictionary/object requirement) is repeated, reducing efficiency.

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?

For a 3-parameter write tool with no annotations and no output schema, the description is moderately complete: it covers the main operation, duplicate behavior, and critical parameter details. However, it lacks information about return values, error conditions, or what happens with invalid inputs, leaving gaps in operational understanding.

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?

With 67% schema description coverage, the description compensates well by adding crucial semantics: it explains the auto_parameter must be a dictionary/object (not JSON string), provides a complete example structure, and clarifies how to disable it. This adds significant value beyond the schema, though it doesn't detail notes_list structure beyond what's in the schema.

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 specific action ('Create multiple notes in a single batch operation') and resource ('notes'), distinguishing it from sibling tools like 'create_note' (singular) and 'update_notes_bulk' (updates rather than creates). It also mentions the efficiency benefit and duplicate handling, which adds valuable context.

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 clear context for when to use this tool ('for efficiency' in batch operations) and implies an alternative by mentioning duplicate handling, which suggests it's suitable for bulk imports. However, it doesn't explicitly state when not to use it or name specific sibling alternatives like 'create_note' for single notes.

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