finance_collections_priority

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

With no annotations, the description must fully disclose behavior. It only mentions routing through a dispatcher under JWT/tenant scope. There is no indication of side effects, idempotency, read-only vs mutation, or response structure.

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 uses an Args bullet list. It is efficient, though the first sentence could more directly state the purpose. No redundant information.

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 the complexity of a domain agent action with an output schema, the description omits critical context: what the action does, what the output contains, prerequisites, and how it integrates with the dispatcher. It feels incomplete.

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 coverage is 0%, so the description must compensate. It adds that 'message' is a free-text objective and 'inputs' is an optional JSON string, which is useful but lacks constraints, examples, or format details.

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 collections_priority' which identifies the tool but does not clarify what collections priority entails or how it differs from many sibling finance tools. The verb 'Run' is generic and the resource is abstract, lacking specificity.

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 on when to use this tool versus alternatives like finance_collections_to_crm_tasks or other finance actions. There is no mention of prerequisites, context, or exclusions.

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