customer_success_finance_subscription_renewal_sweep

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

Annotations flag destructiveHint=true, idempotentHint=false, and openWorldHint=true, yet the description is silent on what the sweep modifies, what side effects occur, or any caution. The only added behavioral content is that it routes through the domain-agent dispatcher under JWT/tenant/company scope — genuine but minor context. No contradiction with annotations, but for a destructive action this is a significant disclosure gap.

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?

Compact and well-ordered: action identity first, routing context second, then a clean Args block that maps directly to the schema. No redundant prose or filler; every sentence earns its place given the thin content.

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, open-world, non-idempotent action with near-twin siblings, the description omits outcome semantics, effect disclosure, and selection guidance — all substantive gaps. The output schema may cover return values, but the missing behavioral and disambiguation context makes this incomplete for safe and correct invocation.

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, and it does provide one-line meanings for both params: message as 'Free-text objective' and inputs as 'Optional JSON string of structured inputs'. This is minimum-viable documentation, but it omits an example of the inputs JSON, what keys/format are expected, and how message and inputs interact — especially important for a generic dispatcher wrapper whose inputs are otherwise opaque.

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 essentially restates the tool name: 'Run the customer_success domain agent action finance_subscription_renewal_sweep' adds no semantics beyond the identifier itself. The routing note (JWT/tenant/company dispatcher) clarifies the mechanism but not what a 'subscription_renewal_sweep' actually does. It also fails to disambiguate from the near-identical sibling customer_success_finance_subscription_renewal_status.

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 exists anywhere in the description. With a large family of overlapping siblings (customer_success_renewal_pipeline, customer_success_finance_subscription_renewal_status, finance_subscription_renewal_sweep, dispatch_domain_agent), an agent gets no selection criteria to pick this tool over alternatives.

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