stripe_run_workflow

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

No annotations exist, so the description must convey behavior. It only states 'high-level composite workflow' without explaining side effects, resource mutations, permissions, or operational impact. The workflow names hint at actions like recovery and outreach, but no explicit behavioral disclosure.

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 and includes the essential information in a readable format. It could be more structured with bullet points or subheadings, but it is concise and functional.

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?

Despite having only one parameter and an output schema, the description lacks contextual completeness. It does not explain the output, behavior, or when to invoke this tool. For a composite workflow tool, more context on the orchestrated steps is needed.

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 schema has 0% description coverage, and the parameter is simply a string. The description adds the allowed workflow values, which clarifies the input. However, it does not describe what each workflow does or any constraints beyond the list.

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 it runs a high-level composite workflow and lists four specific workflow names, making the purpose well-defined. However, it does not explicitly differentiate from sibling stripe tools that may have overlapping functionality.

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 is provided on when to use this tool versus alternatives like individual stripe API tools. There is no mention of prerequisites, when to avoid, or comparison with other workflow-related tools.

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