aggregate_records

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

Lists blocked stages ($out, $merge, $lookup, $facet), implying read-only behavior but no explicit statement. Lacks details on side effects, auth, or output format.

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?

Efficient one-sentence description with key constraint (blocked stages). Could be slightly more structured but is 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?

Incomplete for a data query tool: no info on return format, error handling, or parameter details. Missing details that would help an agent use it confidently.

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 0% and description adds no meaning beyond parameter names. Does not explain 'entity_name' or format of 'pipeline'.

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?

Clearly states it runs a MongoDB aggregation pipeline, including blocked stages. Could better differentiate from read_records for simple queries.

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 on when to use this tool vs alternatives like read_records. Only lists blocked stages, which is more behavioral than usage.

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