customer_success_renewal_pipeline

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

Annotations already mark the tool as destructiveHint=true and non-idempotent, and the description does not contradict that. It adds useful routing and scoping context ('Routes through the platform's domain-agent dispatcher under your JWT, tenant, and company scope'), but it does not disclose what side effects the renewal pipeline may cause.

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 compact and front-loaded with the action being invoked, followed by routing context and parameter explanations. Every sentence earns its place and there is no filler.

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 two-parameter wrapper with an output schema, the description is mostly adequate. However, it does not explain what running a renewal pipeline actually does, when it is appropriate, or what kind of objective and structured inputs are expected, so an agent must rely heavily on the tool name.

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 provides only names, types, and defaults, so the description's Arg notes are the only source of meaning: message is a free-text objective and inputs is an optional JSON string. This is helpful, though it does not detail what structured inputs the action expects.

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 first sentence is specific: 'Run the customer_success domain agent action `renewal_pipeline`' identifies the verb, the domain, and the exact action. It is clear about what the tool does, but it does not explicitly differentiate itself from sibling renewal-related tools such as company_renewals or finance_subscription_renewal_sweep.

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 is provided about when to use this tool versus alternatives like dispatch_domain_agent or other renewal tools. The description only explains what it does and how routing works, leaving the agent to infer applicability from the name.

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