find-cards

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

With no annotations, the description carries the disclosure burden. It discloses that field content is truncated, results are capped, and the output includes note IDs, note type, tags, and excerpts. It does not mention auth, exact caps, or ordering, but for a read-only search tool the disclosed behavior is substantially transparent.

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 four sentences, front-loads the core purpose, then gives the usage context, limitations, and examples. Every sentence earns its place with no redundancy or filler.

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 tool with a single parameter, no output schema, and no annotations, the description covers the essential information: what it searches, what it returns, how to use the query, and the main limitations. It could add the exact truncation cap or result format, but the existing content is sufficient for correct invocation.

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 already describes the query parameter, so the baseline is 3. The description adds value by giving concrete Anki query syntax examples and explaining the consequence of overly broad queries, which helps the agent choose an effective parameter value.

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 opens with a specific verb and resource ('Search for notes using Anki's search syntax') and enumerates the returned fields (note IDs, note type, tags, excerpts). It also explicitly positions the tool as the prerequisite for update-card, update-cloze-card, and delete-card, clearly differentiating it from the sibling create/update/delete tools.

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?

It explicitly states when to use the tool: to obtain the noteId needed by update-card, update-cloze-card, or delete-card. It also warns that results are truncated and capped and instructs the agent to narrow the query if the desired note is not listed, which is actionable usage guidance.

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