reverse

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. 'Reverse pattern' doesn't indicate whether this is a read-only operation, whether it modifies data in-place, what permissions might be required, or what side effects occur. The description provides no behavioral context beyond the basic operation name.

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 extremely concise (two words) but this brevity comes at the cost of meaningful information. While there's no wasted text, the description is under-specified rather than efficiently informative. It's front-loaded by necessity but fails to provide the minimal context needed for effective tool selection.

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?

Given the complexity implied by the sibling tools (musical/pattern manipulation context), no annotations, no output schema, and a completely minimal description, this is severely incomplete. The description fails to explain what 'pattern' means in this context, what 'reverse' operation performs, what the result looks like, or how this differs from similar operations among the many sibling tools.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description doesn't need to compensate for any parameter gaps. While it doesn't add any parameter-specific information (which isn't needed), it maintains the baseline appropriate for a parameterless tool.

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 'Reverse pattern' is a tautology that essentially restates the tool name without adding meaningful context. It doesn't specify what 'pattern' refers to (musical pattern, data pattern, etc.) or what 'reverse' operation actually performs. While it distinguishes from some siblings like 'transpose' or 'stretch', it doesn't clarify how it differs from similar operations like 'undo' or 'generate_variation'.

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 no guidance on when to use this tool versus alternatives. There's no mention of appropriate contexts, prerequisites, or when other tools like 'undo', 'generate_variation', or 'ai_suggest_variations' might be more suitable. The agent receives zero usage direction beyond the tool name itself.

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