get_stats

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

With no annotations, the description must disclose behavioral traits. It only states 'Get database statistics' but does not confirm read-only nature, potential side effects, authentication requirements, or any limitations. The description is too brief to provide sufficient transparency for a tool with no annotations.

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 very concise with two sentences and no unnecessary words. However, the second sentence ('Returns: Stats object...') could be integrated or expanded. It is front-loaded but could be more efficient by combining.

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 no output schema and no annotations, the description is incomplete. It does not specify what 'counts and storage info' includes, how to interpret the stats, or any caveats. For a simple tool, more context would be helpful to avoid confusion with similar siblings.

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 input schema has zero parameters and 100% schema description coverage. According to guidelines, baseline is 3. The description adds no parameter information beyond the schema, but the return description ('Stats object with counts and storage info') provides some minimal context. No extra value.

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 states the tool's purpose ('Get database statistics') and mentions the return type ('Stats object with counts and storage info'). However, it does not explicitly differentiate from sibling tools like query_document_stats, which may also return statistics. The verb 'get' and resource 'database statistics' are specific but lack distinguishing features.

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?

No guidance is provided on when to use this tool versus alternatives. There is no clarification of prerequisites, context, or situations where this tool is preferred or not. The description gives no usage instructions beyond the basic purpose.

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