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

With no annotations provided, the description carries the behavioral burden. It discloses major side effects: sends real emails, requires a specific confirmation string, is not retroactive, and depends on prior testing and account permissions. This goes beyond the schema by adding safety-relevant context, though it does not mention error behavior or return values.

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 front-loaded with the main action, then lists prerequisites and a key limitation (non-retroactive) in two dense sentences. Every sentence earns its place, and there is no fluff, making it highly concise and well-structured.

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 tool has 3 parameters, no output schema, and no annotations, the description covers the essential aspects: purpose, side effects, prerequisites, and behavioral constraints. It does not describe return values or failure modes, but for an action that arms a flow, this is sufficient.

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 description coverage is 67% (flow_id lacks a description). The description mentions the 'confirm' requirement but merely restates what the schema already says ('debe ser exactamente "ARMAR ENVIOS"'). It does not explain flow_id or acknowledge_no_list_filter, though flow_id is self-explanatory from context.

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 purpose: 'ARMA la automatización' (arms the automation) and specifies the consequence: 'a partir de aquí envía correos REALES sola' (from here it sends real emails on its own). This distinguishes it from siblings like test_flow or activate_flow by emphasizing real sends and non-retroactivity.

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 explicit prerequisites: literal confirmation with 'ARMAR ENVIOS', prior flow testing, and account permission for agent sends. This implies the tool should be used after test_flow and only when ready for real sends, giving clear usage context even though no alternative tools are explicitly named.

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