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

No annotations are provided, so the description carries full burden. It only says 'Counts' without disclosing whether this is read-only, what 'the keeping' refers to, or what output shape/results look like. Lacks performance, permission, or grouping details.

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 very short (one sentence), but it sacrifices clarity for brevity. It is front-loaded with the verb, yet the cryptic phrase 'the keeping' forces the reader to guess. Not every word 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?

With no output schema and no annotations, the description must explain what counts are returned. It mentions total, shelf, and surface, but doesn't clarify the meaning of 'the keeping' or the exact structure. Simple tool, but incomplete for a new agent.

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 input schema has zero parameters, and schema coverage is 100% (vacuous). Per baseline for 0-param tools, this scores a 4. The description's mention of 'by shelf, by surface' hints at output dimensions rather than input parameters, which is fine.

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 action ('Counts') and mentions breakdowns (total, shelf, surface), so it's clearly a stats tool. However, 'the keeping' is an unexplained domain term, making the resource ambiguous. It does not explicitly distinguish from sibling tools like cards_browse, though the stats angle helps.

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?

No guidance on when to use this tool versus alternatives like cards_browse or card_get. The context is implied (counts/statistics), but there is no explicit mention of use cases or exclusions.

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