integrations_submit_options_flow_step

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

Without annotations, the description must disclose behavioral traits, but it fails to do so. It does not mention side effects, required prior state (e.g., an active flow), or return behavior. The agent cannot infer what happens upon submission.

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 a single sentence, which is concise but overly terse. While it avoids waste, it sacrifices necessary detail. Every sentence should earn its place; this one does not provide enough value.

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 presence of sibling tools and the complexity of options flows, the description is severely incomplete. It does not explain what an options flow step entails, how 'user_input' should be structured, or what the output schema contains.

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, yet the description provides no parameter information. It does not clarify the role of 'flow_id' or the structure of 'user_input,' leaving the agent to guess their meanings.

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 action 'Submit' and the resource 'a step in an options flow.' It is specific and distinguishes from sibling tools like 'integrations_submit_config_flow_step' by including 'options' in the name, though the description itself does not elaborate on the difference.

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 no guidance on when to use this tool versus alternatives like 'integrations_start_options_flow' or 'integrations_abort_options_flow.' There is no mention of prerequisites or context.

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