Enable/Disable Flow

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

Annotations already indicate idempotent and non-destructive. The description adds the important behavioral note that 'disabled flows won't trigger', which goes beyond annotations. No contradictions.

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?

Two concise sentences, front-loaded with the main action. Every sentence adds value: the first states the operation, the second gives a behavioral consequence and a usage hint.

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 boolean toggle tool with good annotations and no output schema, the description covers the necessary context: what it does, effect, and how to obtain the required ID. No gaps.

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 both id and enabled fully described. The description adds no additional parameter semantics but the mention of list_flows indirectly helps with id. 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?

Specifies the exact verb 'enable or disable' and the resource 'flow automation'. Clearly distinguishes from sibling tools like trigger_flow or update_flow by focusing on the enabled state. Adds context that disabled flows won't trigger.

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?

Provides explicit guidance to use list_flows to find the flow ID, a prerequisite. While it doesn't explicitly state when not to use this tool, the purpose is clear enough to differentiate from sibling tools like get_flow or update_flow.

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