List my decks

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real behavioral detail beyond them: the auth requirement (AnkiWeb session), the ordering guarantee (parents before subdecks), and the return contents (due counts and card totals).

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?

Two sentences with no filler; the resource and scope lead, followed by the ordering/return detail and the auth requirement. Every clause carries information.

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 an output schema exists, the description needn't detail return shape, yet it usefully summarizes it; with no parameters and annotations covering safety, the definition is complete 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?

There are zero input parameters, so the baseline is 4; no parameter meaning needs to be added or is missing.

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?

States a specific verb (List) and resource (decks synced to the signed-in AnkiWeb account), and scopes it as the user's own decks, which cleanly separates it from the shared-deck siblings (search_shared_decks, get_shared_deck).

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 'signed-in AnkiWeb account' scoping implies this is for the user's own synced decks rather than shared decks, and 'Needs an AnkiWeb session' gives a precondition. It stops short of explicitly naming when to prefer a sibling, so it isn't a full 5.

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