reorder_whatsapp_workflows

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

Description includes '[mutation]' hinting at state change, but no annotations exist. It fails to disclose critical behaviors like whether it replaces the entire order, validates IDs, handles conflicts, or returns a result. The tool's mutation nature and lack of detail lower transparency.

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?

Description is a single, concise sentence with no filler. It efficiently conveys the tool's purpose and mutation hint without unnecessary words.

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 one-parameter mutation tool, the description covers the basic purpose but omits return values, error handling, and prerequisites. Without annotations, more completeness would be beneficial, but it's minimally adequate.

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 coverage is 100% with a description for the 'order' parameter. The tool description does not add any meaning beyond what the schema already provides (array of {id, priority}). Baseline score of 3 applies.

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?

Description clearly states 'Reorder workflows' with the specific action of changing execution order of WhatsApp workflows. It uses a specific verb ('Reordenar'/'Reorder') and resource ('workflows'), and distinguishes from siblings like create, delete, update, toggle, or bulk actions.

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 usage for reordering workflows but provides no explicit 'when to use' or 'when not to use' guidance. Given the many sibling tools for workflow management (create, delete, toggle, etc.), the lack of usage context is a gap.

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