parse_aggregate

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions the requirement for a master key, which is useful. However, it does not disclose potential side effects (e.g., aggregation pipelines with $out or $merge which can write data) or performance implications, leaving some ambiguity.

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 three short sentences, front-loaded with the core purpose, and contains no redundant information. Every sentence earns its place: what it does, the auth requirement, and when to use it.

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?

The tool is moderately complex with nested parameters and no output schema. The description explains the purpose, gives pipeline examples, and notes the master key requirement. However, it lacks details on return format, potential write operations within pipelines, or usage examples, leaving room for improvement.

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 schema descriptions are minimal, and the description provides no additional details about className. It does add value by listing example pipeline stages (match, group, sort, project), but this only partially compensates for the lack of parameter-level guidance.

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 executes advanced aggregation queries using a MongoDB pipeline, listing typical stages like match, group, sort, and project. The verb 'Ejecuta' is specific, and the pipeline mention distinguishes it from simpler query tools like parse_query.

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 clear usage context by stating it is useful for statistics, aggregations, and complex calculations. It does not explicitly contrast with sibling tools, but the 'advanced' qualifier and pipeline explanation imply when to prefer it over simpler query tools.

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