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

With no annotations provided, the description must carry behavioral disclosure. It conveys that this is a read-only statistics tool by listing aggregate measures like published records and unique source documents, which implies no mutation. However, it does not disclose details such as data freshness, access requirements, or any operational limitations.

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, well-structured sentence with the core purpose front-loaded before a colon and a concise list of outputs. There is no redundant wording or filler, and every element contributes to understanding the tool.

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 zero-parameter, low-complexity statistics tool, the description is nearly complete: it names the corpus and enumerates the main return categories. It does not provide an exact output schema, but the listed categories are sufficient for an agent to know what to expect. Additional detail on return format would be nice but is not essential given the tool's simplicity.

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 has zero parameters, so there is no parameter semantics for the description to explain. The description adds value by enumerating the dimensions of statistics the tool returns, which helps an agent understand the output despite the empty input schema. This meets the baseline expectation for a no-parameter tool.

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 resource as the Assetize corpus and the action as providing coverage/transparency stats, listing the specific stat categories. It distinguishes the tool from siblings, none of which are about corpus coverage. The only minor weakness is the absence of an explicit verb like 'returns' or 'gets,' but the meaning is unambiguous.

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 implies its usage context well: an agent should call this tool when it needs corpus-level coverage or transparency statistics. No alternatives are named, but no sibling tool overlaps with this responsibility, and there are no exclusions to state. The context is clear enough for an agent to decide when to invoke it.

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