ecp_mongo_create_collection

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely repeats the operation ('create') and provides no detail on side effects, permissions, idempotency, failure modes, or behavior when the collection already exists. This is barely more informative than the tool name itself.

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 one short sentence with no filler and is front-loaded. However, it is under-specified rather than efficiently complete; its brevity comes at the cost of nearly all useful context.

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 two-parameter creation tool with no annotations and no output schema, the description omits important context: prerequisites, what happens on duplicate creation, return behavior, and which sibling operations are relevant. The large sibling list of Mongo tools increases ambiguity, making this description incomplete.

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 0%, and the description adds no meaning to db_name or collection_name beyond the schema's plain string types. There are no format hints, constraints, examples, or clarification about what values are valid. The description fails to compensate for the undocumented parameters.

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 states a clear verb+object: 'Create a collection in a database.' It unambiguously identifies the operation and resource. However, it does not distinguish itself from closely related Mongo tools like ecp_mongo_drop_collection, ecp_mongo_list_collections, or ecp_mongo_create_database, so it misses the top score.

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 given about when to use this tool versus alternatives. It does not mention whether the database must already exist, how it relates to ecp_mongo_create_database, or contrast with list/drop collection operations. An agent is left to infer usage entirely from the tool name.

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