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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), so the bar is lower, and the description still adds real interpretive caveats: illustrated channels are excluded, pending candidates inflate directory counts, and AI status counts do not constitute reviewed avatar evidence. Only the meaning of 'snapshot methodology' is left unexplained.

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?

Four short sentences, front-loaded with the return payload, each carrying a distinct caveat. Mild deduction for the cryptic 'Metadata separates the full research archive from directory coverage', which is not obvious on first read.

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 parameters, rich annotations, and an output schema covering the return shape, the description only needs to prevent misinterpretation of the numbers — which it largely does. The unexplained 'metadata' field reference is the one loose end for an agent reading results.

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 takes zero parameters, so the baseline is 4; the description correctly spends no words on arguments and instead clarifies what the counts mean.

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?

Specific verb and resource: returns directory record/source counts, AI status counts, and snapshot methodology. It is clearly a coverage/statistics tool, distinguishable in spirit from the sibling retrieval tools (get_ai_monk, search_ai_monks), though no sibling is named explicitly.

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 statement of when to call this versus get_ai_monk or search_ai_monks — e.g., 'use to gauge coverage before searching'. The remaining sentences describe how to interpret counts, not when to invoke the tool.

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