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

No annotations are provided, so the description must carry the behavioral burden. It does disclose operations: pushing cards and ledger, reading back all cards, and clearing ids. Yet it omits permissions, reversibility, side effects of clearing, rate limits, and return behavior, so it is only partially complete.

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 two short sentences, front-loaded with purpose and then an exclusion. There is no filler, though 'Internal' and 'Not for conversational use' are somewhat redundant and the parenthetical packs three operations densely.

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 4-parameter internal sync tool with no annotations, no output schema, and 0% schema description coverage, the description is thin. It lacks the key parameter's purpose, return semantics, and operational handling details, leaving an agent without enough to invoke it confidently.

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 0% for 4 parameters. The description indirectly relates to cards, ledger, and clear (ids), but never addresses the 'key' parameter and gives no format or role details. It only partially compensates for the total lack of schema documentation.

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 the tool's purpose as an internal mirror sync and enumerates its operations (push cards + ledger, read back all cards, clear ids). This is a clear verb+resource, but it does not distinguish itself from sibling editor_* or other tools, so it falls short of a 5.

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 provides an exclusion ('Not for conversational use') and labels itself 'Internal', which implies intended usage. However, it gives no positive when-to-use context or named alternatives among the many siblings, leaving usage largely implied.

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