find_cards

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

With no annotations provided, the description carries full burden. It clearly explains the query syntax, the return fields (deck, note, interval, due, suspended state), and the limit cap. It does not mention side effects, but as a search tool, read-only behavior is assumed.

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 extremely concise with two sentences. The first sentence states the action and syntax, the second lists returns and limit. No superfluous words, making it easy for an agent to parse quickly.

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 the tool has 2 parameters, an output schema (though not shown), and no annotations, the description covers key return values, query syntax, and limit behavior. It does not mention error handling, sorting, or whether all IDs are returned regardless of limit, but overall it's fairly complete for a search tool.

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 0%, so the description must compensate. It explains that 'query' uses Anki's query syntax and that 'limit' caps returned detailed info. It adds meaningful context beyond the schema types, though it does not detail the query syntax format.

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 specifies the verb 'Search', the resource 'cards', and the use of 'Anki's query syntax'. It explicitly lists the return values (count, IDs, detailed info) and the limit behavior, distinguishing it from siblings like find_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 implies usage for searching cards via Anki's query syntax. Although it doesn't explicitly state when not to use or name alternatives, the context and sibling list make it clear that this is for card-level queries vs note-level queries (find_notes).

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