finance_collections_to_crm_tasks

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

Annotations already signal destructive and non-idempotent behavior. The description adds only routing/auth context and does not describe what side effects occur, what data is written, or what 'running the action' actually changes. It neither contradicts nor meaningfully supplements the annotations.

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 short and readable, with a brief Args section. However, the opening sentence largely repeats the tool name, and the routing detail consumes space that could have been used to explain the action's semantics. It is compact but under-informative.

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?

Given a destructive, non-idempotent action with free-form parameters, an agent needs more than 'run this action' to invoke it safely. The description does not explain what happens on execution, what inputs are expected, what the output represents, or what prerequisites exist. The presence of an output schema lowers this burden somewhat, but the missing behavioral context remains a significant gap.

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. It provides only generic definitions: 'message' is a free-text objective and 'inputs' is an optional JSON string. It does not specify expected keys, formats, examples, or how these map to the finance action's actual 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?

The description states 'Run the finance domain agent action finance_collections_to_crm_tasks', which essentially restates the tool name. It adds routing mechanics but never explains the actual purpose, such as turning collections data into CRM tasks, so an agent cannot tell what this tool accomplishes.

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 like create_crm_task or other finance_* actions. The description only mentions that it routes through a dispatcher under JWT, tenant, and company scope, which is infrastructure detail rather than usage context.

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