Modify an existing Anki card's fields and tags by note ID to correct or refresh card content.
Update an existing card in Anki
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | New tags for the card | |
| fields | Yes | Fields to update | |
| noteId | Yes | ID of the note to update |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. 'Update' implies mutation but it doesn't state whether changes require auth, are reversible, what happens to tags/fields not specified, or any side effects. Significant gap for a mutation 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?
A single efficient sentence that front-loads the verb and resource. No waste, but also no additional structure or detail.
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 mutation tool with nested objects, no annotations, and no output schema, the description is far too thin. It omits behavior, side effects, and usage context that an agent needs to call it correctly.
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% and the schema fully documents noteId, fields, and tags. The description adds no parameter meaning beyond the schema. Baseline 3 is appropriate.
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?
Clear verb 'update' and resource 'card' with system context 'in Anki'. Doesn't distinguish from sibling create_card or specify what a card is vs a note, but the operation is unambiguous.
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?
No guidance on when to use this vs create_card, search_cards, or any sibling. No prerequisites stated. An agent must infer usage entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.