integrations_abort_config_flow

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

With no annotations, the description must fully disclose behavior. It only states 'Abort a config flow in progress' without explaining side effects, whether resources are cleaned up, or if the flow can be aborted at any step. This is insufficient for a mutation tool.

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 one sentence of six words, perfectly concise and front-loaded. Every word is necessary and serves the purpose.

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 tool with 1 parameter and no annotations, the description is too sparse. It omits context about when a config flow can be aborted, confirmation of success, and any implications. While output schema exists, behavioral completeness is lacking.

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 input schema has 0% description coverage for the flow_id parameter. The description does not explain what flow_id represents or how to obtain it, leaving the agent to infer from the parameter name alone. The description adds no value beyond the schema.

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 'Abort a config flow in progress,' using a specific verb and resource. It distinguishes this tool from sibling tools like start_config_flow, submit_config_flow_step, etc., by its action of aborting an existing flow.

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 usage guidelines are provided. The description doesn't indicate when to use this tool versus alternatives (e.g., when to abort vs. remove an integration), nor does it mention prerequisites or post-conditions.

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