sub_add_dunning

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says it generates dunning/recovery and is a Pro feature; it does not disclose whether files are written, whether an API key is required, what side effects occur, or whether this mutates an existing subscription system.

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 short sentence with no filler and the action is front-loaded. It is structurally efficient, though the brevity sacrifices explanatory depth.

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 tool with no annotations, no output schema, an undocumented parameter, and no sibling differentiation, this description is not complete enough for an agent to reliably select and invoke it. Important context about what is generated, where, and under what conditions is left to inference.

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 50%: directory is minimally documented as 'Project directory', while api_key has no description. The description adds no parameter meaning, so it does not compensate for the undocumented api_key or clarify what the directory should contain or how it is used.

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 states a concrete action ('Generate') and a specific resource ('dunning and recovery'), with a useful Pro-plan qualifier. It is clear enough to identify the tool's domain, though it does not explicitly distinguish it from sibling subscription/billing tools such as sub_add_billing.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no mention of surrounding subscription-generation steps. The 'Pro feature' note hints at an entitlement condition but does not help an agent decide between this and sub_add_billing, invoice_generator, or subscription_billing_setup.

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