Sync with AnkiWeb

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

Annotations already declare the operation is non-read-only, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds the auth precondition, which is genuine context beyond the annotations, but it omits whether sync is one-way or two-way, how conflicts are resolved, and that it requires network access.

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 with the action front-loaded and the precondition in parentheses. Every clause earns its place; nothing is padded or redundant.

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?

With zero parameters, full annotation coverage, and an output schema handling return values, the description covers the essentials. The remaining gap is that sync direction and conflict behavior for a state-changing collection operation go unmentioned.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not waste space restating an empty 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?

States a specific verb and resource: 'Sync the collection with AnkiWeb'. No sibling tool does syncing, so the agent can distinguish it from the list/find/create/delete siblings without ambiguity, though the description never explicitly contrasts itself with them.

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 precondition 'requires being logged in to AnkiWeb in Anki' is a useful usage constraint that tells the agent when the call will fail. However, it gives no guidance on when syncing is warranted (e.g., after local mutations) or what to do if not logged in, so usage is only implied.

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