prepend

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

With no annotations, the description carries the full burden. It usefully discloses a key edge case: if the Value is an Array, a flat array is returned with each item prepended. However, it does not clarify whether the original array is mutated or a new array is returned, which is a common ambiguity in array operations.

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 two sentences, front-loaded with the primary action and then adding a concise edge case. Every word earns its place; no fluff or repetition.

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 simple array operation, the description covers the core behavior and a notable edge case, and states the return value. However, it omits mutation semantics and potential error conditions. Given the lack of output schema and annotations, it is reasonably complete but not exhaustive.

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 input schema has zero properties, so the description is the only source. It names the two conceptual inputs (Array and Value) and explains their relationship. Since there are 0 parameters in the schema, the baseline is 4, and the description adds enough meaning to justify that score, though it lacks explicit parameter names/order.

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 action: adding a Value as the first item of an Array and returning the result. It uses a specific verb ('prepend') and distinctly describes the operation, differentiating it from sibling tools like 'reverse' or 'removefirst'.

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 implies the use case ('Given an Array and a Value') but provides no explicit guidance on when to choose this over alternatives. It does not mention any exclusions or alternative tools, so the usage context is only inferred.

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