Search community shared decks on AnkiWeb by query and return matching deck results, with an optional limit.
Search community shared decks on AnkiWeb. Optional: search, limit (default: 50). Returns array of SharedDeck. (public)
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of shared decks to return | |
| search | No | Query term to search shared decks |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds that results are an array of SharedDeck and that the search is public, but it does not mention pagination, rate limits, or result variability beyond what the annotations imply.
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 compact and front-loaded, with no wasted sentences. It covers purpose, parameters, default, return type, and public visibility in a very small space.
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 simple two-parameter search tool with full schema coverage and clear annotations, the description provides enough context to call it correctly. It names the return type even though there is no output schema, though it omits any detail about SharedDeck fields or pagination behavior.
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 both parameters. The description adds useful semantics by stating both parameters are optional and that limit defaults to 50, which is not specified 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 states a specific verb and resource: 'Search community shared decks on AnkiWeb.' It is clear what the tool does, but it does not explicitly differentiate from related siblings such as shared_brief, shared_info, or the generic search tool.
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?
Usage is only implied by the tool's purpose. There is no explicit guidance on when to use shared_search versus sibling tools like search, shared_brief, or shared_info, nor any stated exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.