get_collections_worklist

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

With no annotations, the description carries the full burden of behavioral disclosure, but it does not state whether this is a read-only operation, how results are ordered beyond 'rank', whether it returns a limited list, or what the output contains. The tool name 'get' weakly implies read-only, but the description itself provides no such guarantee.

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 one concise, front-loaded sentence with no filler words. It communicates the core purpose efficiently, though the brevity contributes to the completeness gaps penalized in other dimensions.

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 no annotations, no output schema, and a low-parameter-documentation schema, the description is insufficient on its own. An agent still needs to know how optional parameters behave (e.g., defaults, limits), what date semantics apply, and how this differs from get_ar_aging.

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 only 33% (only asOfDate has a format hint), and the description does not explain topN, overdueMoreThanDays, or their defaults and interactions. 'Overdue receivables' only vaguely hints at overdueMoreThanDays; the agent gets no meaningful parameter guidance.

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 uses a specific verb ('Rank') and identifies the resource ('overdue receivables') and the ranking criterion ('customer risk score') for collections prioritization. It is clear on what the tool does, though it does not explicitly differentiate it from similar receivables/aging tools like get_ar_aging.

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?

The phrase 'for collections prioritization' implies a use case, but there is no guidance on when to use this tool versus siblings such as get_ar_aging or get_top_customers. No exclusions, prerequisites, or alternative conditions are provided.

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