Get a shared deck

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds a genuinely useful behavioral fact beyond them — that no AnkiWeb session is required — which tells the agent this works before authentication. No rate-limit or caching behavior is disclosed, but the auth note is solid added value.

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 sentence that front-loads the verb and resource and then lists the returned fields efficiently. No filler, every clause earns its place.

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 read-only tool with full annotations and an output schema, the description is nearly complete. The only meaningful gap is the absence of routing guidance relative to search_shared_decks and download_shared_deck; return values need not be explained since an output schema exists.

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%, so both the deck id/URL format and the reviews count/default are already documented in the schema. The description adds nothing about either parameter, so the baseline 3 applies.

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 ('Read') and resource ('shared deck's AnkiWeb listing') and enumerates exactly what the listing contains: description, tags, size, ratings, sample notes with media, and reviews. This plainly distinguishes it from siblings like download_shared_deck (which fetches files) and search_shared_decks (which finds ids).

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: an agent can infer this is the metadata-inspection step before downloading, but no alternative sibling (search_shared_decks, download_shared_deck) is named and no when/when-not condition is given. The 'needs no AnkiWeb session' note is a precondition, not routing guidance.

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