mongo_collection_stats

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

With no annotations, the description carries full burden. It discloses that the tool retrieves storage, index size, and document count stats, but does not mention any behavioral traits like read-only nature, side effects, permissions required, or impact on performance. It also omits that the tool might work only with a valid connection ID.

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, concise sentence of 12 words. It is front-loaded with the action and resource, with no extraneous information.

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 simple statistics tool with three parameters and no output schema, the description provides the core purpose. However, it lacks parameter explanations and usage context, which could help an agent select and invoke it correctly. Sibling tools like mongo_explain or mongo_db_stats are not distinguished, reducing completeness.

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 coverage is only 33% (only connectionId has a description). The description does not add meaning for the 'database' or 'collection' parameters beyond the schema. It mentions 'collection' in the tool purpose but does not clarify that 'database' is optional or how it affects the query.

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 verb 'Get' and the resource 'detailed storage, index size, and document count statistics for a MongoDB collection.' It distinguishes this tool from siblings like mongo_list_collections (lists collections) and mongo_db_stats (database-level stats), as it focuses on collection-level statistics.

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 explicit guidance is provided on when to use this tool versus alternatives. The description does not mention when not to use it, prerequisites, or suggest other tools for different needs (e.g., using mongo_db_stats for database-level stats).

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