map_reduce_mr_sort

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

No annotations provided; description only mentions default ascending order. Lacks details on stability, mutability, handling of nulls, or whether the input is modified or returned as new array.

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?

Single sentence, no redundancy, front-loaded with key info. However, it is overly brief given the tool's complexity and lack of supporting annotations.

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?

Despite having an output schema, the description does not cover error conditions, input validation, or edge cases. With no annotations, more context is needed for reliable use.

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 has 0% description coverage; the tool description adds only a hint about the 'reverse' parameter via 'ascending by default'. Does not explain 'data' (expected format: JSON array string) or 'field' (field name syntax).

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 sorts a JSON array by a field, with ascending default. It uses a specific verb and resource, and is distinct from sibling tools like mr_filter, mr_group, etc.

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 sorting vs other operations. No mention of prerequisites, when to choose this over alternatives, or what scenarios are appropriate.

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