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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It names the categories included but never states whether the tool returns counts, detailed records, or some other summary structure. With no output schema, the return shape is undefined, and the description does not even explicitly confirm the operation is read-only.

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 compact sentence that front-loads the tool's scope and wastes no words. It is appropriately concise, though the brevity contributes to some ambiguity about what the tool actually returns.

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 tool, invocation setup is trivial, but the absence of an output schema means the description must explain what the response represents. The category list is helpful, but 'what this deployment holds' does not clearly specify that the result is a summary or count-based stats object. An agent would still be guessing about the response format.

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 accepts zero parameters, so the input schema fully covers parameter semantics. The description adds no parameter-specific meaning, but none is needed when there are no parameters. Baseline 4 applies.

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 communicates that the tool provides an aggregate view of a deployment's contents, listing five concrete categories (collections, sources, items, items added today, feeds). It lacks an explicit verb like 'returns' or 'counts,' but the name 'stats' combined with the phrasing makes the intended purpose reasonably clear. It does not explicitly differentiate from sibling list tools, though the aggregate nature is subtly implied.

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 instead of sibling tools like list_feeds, list_sources, or recent_items. An agent must guess whether stats is for counts/summaries and the siblings are for detailed lists. No exclusions, conditions, or alternatives are mentioned.

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