reverse

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

No annotations are provided, so the description carries full burden for behavioral transparency. It states the core action (reverses order) but does not disclose critical behavior such as whether the original array is mutated or a new array is returned. This ambiguity could lead an agent to use the tool incorrectly in a pipeline.

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 with no filler. It front-loads the main verb and includes the essential detail about array data types. No unnecessary words, and the information is easy to parse.

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 has no annotations, no output schema, and a very short description. While the core function is clear, the description fails to address whether the operation mutates the original array, what happens with empty arrays or non-array inputs, and the exact return type. These missing details are important for an agent to safely invoke the 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 schema has 0 parameters, so the baseline is 4. The description adds value by indicating the tool expects an array as input, even though it does not specify how the array is passed (e.g., as an argument or via the current value). This is useful but leaves some ambiguity about the interface.

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's function: reversing the order of an array. It uses a specific verb ('Reverse') and identifies the resource (Array), distinguishing it from siblings like sort or filter. The phrase 'of any data type' adds useful specificity.

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?

Usage is implied: use this when you need to reverse an array. However, there is no explicit guidance about when to use this versus alternatives, nor any exclusions or prerequisites. The description does not mention any specific context or alternatives, so it falls at the 'implied usage' level.

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