finance_stripe_dunning_recovery

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

The description adds useful scope context by saying execution routes through the domain-agent dispatcher under the caller's JWT, tenant, and company scope, which is not captured by the annotations. However, it does not describe the actual side effects, data touched, or what the destructiveHint implies in practice; the safety profile is mostly carried by the annotations rather than 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 short, structured, and free of filler, with the Args section clearly laid out. However, the opening sentence largely restates the tool name, so the structure is tidy but semantically thin.

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 destructive finance action with two generic parameters and hundreds of siblings, this description is not enough for an agent to choose when to call it or what to pass. It omits the actual purpose and expected inputs of the dunning recovery action, and the output schema and annotations do not fill that gap. Only the dispatcher/scoping context is genuinely useful.

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 description coverage is 0%, so the description must compensate. It states that message is a free-text objective and inputs is an optional JSON string, adding a little meaning beyond the bare schema. But it does not explain what structured inputs this specific dunning-recovery action expects, leaving the agent unable to construct a correct invocation.

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 only says to run the action named finance_stripe_dunning_recovery and explains the dispatcher plumbing; it never states what dunning recovery actually does or what outcome to expect. This is close to a tautology and provides no semantic differentiation from finance_stripe_failed_payment_recovery, finance_dunning_outreach, or other finance siblings.

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 when-to-use or when-not-to-use guidance is provided, and no alternative tools are mentioned. The description gives routing mechanics but does not state under what conditions this action should be selected, what prerequisites apply, or what approvals might be required for a destructive operation.

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