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

Annotations already declare the operation read-only and idempotent. The description adds useful behavioral context beyond those annotations: it counts only public works, returns distinct counts, supports combined filters, and explicitly returns no bibliography or text. This is meaningful behavioral disclosure for a read-only aggregate tool.

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?

Two sentences with no filler, and the core purpose is front-loaded. The most important constraints—public scope, distinct counting, combined filters, and no content returned—are stated economically.

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?

Despite a highly complex nested filters schema, no output schema, and zero parameter descriptions, the description explains only the general counting behavior and two filter fields. It does not describe the return shape or clarify the semantics of many filters, so an agent would still face significant uncertainty when constructing a correct call.

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%, so the description carries the burden of explaining the large filters object, but it only highlights baselReferences/baselReferencePrefix as exact-match filters and says filters can be combined. Many opaque parameters such as 'full', 'includeSemantic', 'hasExtractedText', and 'journalScope' remain unexplained, leaving significant semantic gaps.

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 starts with a specific verb ('Count') and explicit resources ('distinct public works, editions and journals'), which precisely identifies the operation. It further distinguishes itself from retrieval tools by stating that no bibliography or text is returned.

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 description makes clear that this tool is for counting, not content retrieval, and that filters can be combined. However, it never explicitly contrasts it with sibling tools like aggregate_catalog, list_works, or search_works, leaving the agent to infer when this is the right choice.

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