get_collection_stats

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states 'get', implying read-only, but fails to explain the output_file parameter's side effects (e.g., writing statistics to a file) or any environment prerequisites such as an open collection. This leaves significant behavioral uncertainty.

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 a single efficient sentence that leads with the main action and the key statistics. It's concise and well-structured, though it omits the parameter explanation—a critical failure, but conciseness itself is strong.

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 that there are no annotations and the parameter has 0% schema coverage, the description is far from complete. An agent cannot invoke the tool correctly without understanding output_file. The high-level purpose is clear, but the operational details necessary for correct invocation are missing.

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 sole parameter output_file is completely undocumented in both the schema and the description (schema coverage 0%). The agent has no way to know its purpose, whether it's optional, or what formats are accepted. The description should have at least mentioned that statistics can be saved to a file if output_file is provided.

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 clearly identifies the verb 'get' and the resource 'collection statistics', and enumerates specific metrics (total notes, cards, new/due cards, deck breakdown). However, it doesn't contrast with sibling tools that also return counts (e.g., search_notes), so it doesn't fully differentiate itself.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention that it's a read-only overview, or that specific deck details might come from list_decks. The agent receives no context to decide between this and other tools.

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