redrive_function_run

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

No annotations are provided, so the description must carry the behavioral transparency burden. It does not disclose important traits such as whether redriving creates a new run, replaces the original, or is idempotent. The 'optional wait' parameter is mentioned but not explained in the description.

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 that efficiently conveys the purpose and key optional features without extraneous text.

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?

The tool has 6 parameters and a nested retry object, but no output schema. The description does not explain the return value (e.g., the new run ID or status), nor does it clarify behaviors like what happens when wait is true vs false. This leaves significant gaps for the agent.

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 description coverage is 83%, so the baseline is 3. The description adds minimal value by listing 'retry override' and 'wait' as options, but these are already apparent from the schema's required/optional fields and property descriptions.

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 ('Redrive') and the specific resource ('failed/cancelled/expired durable function run'), distinguishing it from sibling tools like 'create_function_run' or 'cancel_function_run'.

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 implies usage when a run is in a failed/cancelled/expired state, but does not explicitly exclude other states or provide comparisons to alternatives. It gives clear context but lacks exclusions.

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