finance_credit_risk_to_crm_health

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, so the description does not need to repeat those. It adds useful context about routing under JWT, tenant, and company scope, but it does not disclose what data may be changed or what side effects occur, leaving the destructive behavior unspecified.

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, front-loaded with the action name, and the Args section is clearly structured. It wastes little space, though the opening sentence largely repeats the tool name.

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 two free-form parameters and a domain-agent action name, the description is insufficient for an agent to know what objective to write or what structured inputs to provide. It gives no example, no expected keys, and no behavior. The presence of an output schema does not compensate for missing input semantics.

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 carry parameter meaning. It provides only generic hints: message is a "free-text objective" and inputs is an "Optional JSON string of structured inputs." It does not explain what structured fields the action expects or how inputs relate to the credit-risk-to-CRM-health task, so an agent cannot construct a reliable call.

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 says "Run the finance domain agent action `finance_credit_risk_to_crm_health`" and mentions routing through a dispatcher. This largely restates the tool's name rather than explaining what the action accomplishes, such as how credit-risk data is transformed into CRM health. It does not differentiate this from the many other finance_* and domain-agent sibling tools.

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 given about when to use this tool versus alternatives such as dispatch_domain_agent or finance_collections_to_crm_tasks. The only context is the routing mechanism and scope, not selection criteria.

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