finance_subscription_health_to_expansion

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

Discloses that it routes through the domain-agent dispatcher with JWT/tenant/company scope, but does not describe side effects, mutation behavior, or what the action entails. No annotations provided to compensate.

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?

Description is short and front-loaded, but under-specified. It is not verbose, but lacks necessary detail for an agent to use it effectively.

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 (not shown), the description does not mention return values, prerequisites, or the action's purpose. Incomplete for a domain agent action of likely complexity.

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%. Description adds basic meaning ('free-text objective', 'optional JSON string') but does not explain expected format, structure, or constraints for 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?

Description says it runs a specific action but does not explain what that action does. The name suggests transitioning from subscription health to expansion, but no elaboration. Sibling tools like finance_subscription_renewal_status and finance_subscription_renewal_sweep are not distinguished.

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 alternatives. No context about typical scenarios or exclusions.

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