ecp_mongo_database_sizes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get size' effectively indicates a read-only operation over all MongoDB databases, which is useful, but it does not mention output format, units, or behavior when no databases exist. For such a simple zero-parameter tool this is acceptable but not richly transparent.

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 sentence that immediately states the action and target. There is no filler, repeated information, or unnecessary detail, making it appropriately concise and front-loaded.

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 tool's low complexity, zero parameters, and no output schema, the description is mostly complete for invocation purposes. It tells the agent what will be retrieved, though it does not describe the return shape or any edge cases. The missing output details are minor for this simple read-only tool.

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 has zero parameters and an empty input schema, so the baseline of 4 applies. The description does not need to explain parameters that do not exist, and no parameter documentation gap exists.

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 'size of each MongoDB database', so an agent knows exactly what the tool does. It is not a tautology and is semantically distinct from sibling tools like ecp_mongo_list_databases and the MySQL/MSSQL/PostgreSQL variants, though it does not explicitly name an alternative.

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 implies when to use the tool: when you need size information for MongoDB databases. However, it provides no explicit guidance about alternatives, such as using ecp_mongo_list_databases for database names/status or counterpart tools for other database engines. The usage context is clear enough but not directly stated.

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