bulk_toggle_workflows

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

No annotations provided, so the description carries full burden. It only notes '[mutation]' but does not disclose side effects, required permissions, rate limits, or behavior with invalid workflow_ids. For a mutation tool, this is insufficient.

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 short but contains redundancy: the first line and second line convey the same information. It could be condensed to a single sentence without loss of meaning.

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?

No output schema, so description should clarify return values or confirmation. It lacks details on error handling, idempotency (e.g., toggling already-correct state), or what happens to related resources. Given many sibling tools, more context would help.

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 covers 100% of parameters with clear descriptions. The description adds no additional meaning beyond the schema. Baseline 3 is appropriate.

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 'Activar/desactivar workflows en lote' (activate/deactivate workflows in batch), with a specific verb and resource. It distinguishes from siblings like toggle_whatsapp_workflow (single toggle) and bulk_delete_workflows (delete instead of toggle).

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 this tool versus alternatives. With many workflow-related siblings such as toggle_whatsapp_workflow, bulk_delete_workflows, and toggle_analytics, the description lacks context on when bulk toggle is appropriate or when to use single toggle instead.

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