mongo_db_stats

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

No annotations are provided, so the description must disclose behavioral traits. It only indicates a read operation ("Get") but does not discuss potential performance impact, required permissions, or whether it mutates data. For a diagnostic tool that may run a relatively heavy db.stats() command, this omission is significant.

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 extremely concise (6 words), which ensures front-loading but lacks necessary detail. It is not overly verbose, but the brevity sacrifices clarity on purpose, usage, and output. A slightly longer description could add value without becoming bloated.

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 the absence of an output schema and annotations, the description should at least outline the type of statistics returned (e.g., data size, index sizes, collections count). It does not, leaving the agent uncertain about what information the tool provides, which is incomplete for effective use.

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 50% (connectionId has a description, database does not). The tool description adds no parameter-level information, failing to compensate for the missing schema description of the 'database' parameter. The agent is left without guidance on what values are valid or how to format them.

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 retrieves statistics for a MongoDB database, which distinguishes it from siblings like mongo_collection_stats (collection-level) and mongo_server_status (server-level). However, it does not specify the type of statistics returned, slightly reducing clarity.

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 provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or contexts such as when to prefer mongo_db_stats over mongo_collection_stats. This lack of contextual information makes it challenging for an agent to decide between similar tools.

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