finance_stripe_dunning_recovery

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

No annotations provided; the description fails to disclose any behavioral traits (e.g., side effects, required permissions, data access). The generic routing note adds no value beyond infrastructure context.

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 front-loaded with the action name, which is structurally acceptable. However, it sacrifices substance for brevity, missing essential details.

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 an output schema, the description provides no context about what the tool returns or how it behaves. For a finance action like dunning recovery, the lack of domain-specific information makes it incomplete.

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?

Description adds basic labels ('Free-text objective', 'Optional JSON string') but no detail on expected format or content. With 0% schema coverage, more meaningful guidance is needed for parameters like 'inputs'.

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 repeats the tool's name and says 'Run the finance domain agent action'. It does not explain what 'dunning recovery' entails, lacking a specific verb and resource. The purpose is implied but not clearly stated.

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 on when to use this tool versus sibling tools like finance_stripe_failed_payment_recovery or finance_dunning_outreach. Absence of context or exclusions makes it unhelpful for selection.

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