company_collections

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. It does add one meaningful trait: 'supplied proofs are verified', and it states 'provider effects remain external', suggesting the tool validates inputs without causing provider-side side effects. However, it does not disclose whether 'advance' mutates state, what happens on verification failure, what side effects occur, or any authentication requirements.

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 a single compact sentence with no filler, which is structurally concise. However, its density sacrifices clarity; terms like 'scoped lifecycle' and 'provider effects remain external' are cryptic rather than informative. It is front-loaded with the main action but does not earn its place by providing usable guidance.

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?

Although an output schema exists (so return values need not be described), the description is incomplete for safe invocation. It fails to explain what operations are available beyond inspect/advance, what bundle_json and project_id contain, how proofs are supplied and verified, and when to use this tool among the many related siblings. An agent would need significant additional context to invoke it reliably.

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%, and the description does not clarify any of the seven parameters, including required project_id and bundle_json. 'Supplied proofs are verified' loosely maps to bundle_json possibly carrying proofs, but this is not explicit. No explanation is given for operation, engine, now, entity_ref, or payload_json, leaving the agent to guess how to invoke the tool correctly.

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 a specific action on a resource ('Inspect or advance collections'), which is more than a tautology. However, 'through its scoped lifecycle' is vague jargon, and there is no differentiation from sibling tools like company_receivables, company_dunning, or finance_collections_priority. An agent cannot tell when this tool, rather than those, is the right choice.

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 among the many company_* and finance_collections_* siblings. The phrase 'provider effects remain external' hints at a behavioral boundary but does not say when to choose this tool over others or what operations require which inputs. The default 'operation' is implied to be 'list' but this is not discussed.

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