company_pay_run

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

With zero annotations, the description must carry the full transparency burden. It does volunteer two useful facts—proof verification and external provider effects—but leaves essential behaviors uncovered: what 'advance' mutates, whether there are side effects on internal state, the meaning of 'scoped lifecycle', and any prerequisites or failure modes. This is below the level needed for safe autonomous use.

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 sentence and is not bloated; it front-loads the two actions. However, the phrasing is dense and ambiguous ('scoped lifecycle'), and the sentence contains jargon that likely confuses rather than illuminates. It earns a mid score for economical use of words but loses points for clarity of content.

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?

A tool with 7 parameters, no annotations, 0% schema coverage, and no sibling guidance requires a much richer description to be callable correctly. The output schema exists, but it doesn't tell the agent what to pass or what 'inspect' vs 'advance' does. The description touches on lifecycle and proof verification but leaves every operational detail missing.

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 mention a single parameter (project_id, bundle_json, payload_json, operation, entity_ref, now, engine). With 7 parameters entirely undocumented, the agent cannot understand what values to supply or what operation 'list' versus an advance entails. The description does not compensate whatsoever.

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 names a concrete object ('pay run') and suggests two high-level actions ('inspect or advance'), so an agent can tell it deals with pay runs. However, 'through its scoped lifecycle' is abstract and it never names the operations (list/advance), making it hard to distinguish from siblings like company_pay_run_batch. It lacks a precise, operation-specific statement of what the tool does.

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?

There is no guidance on when to use this tool versus the many pay/run/batch siblings. Neither prerequisites, nor exclusions, nor a recommended context is provided. The sentence 'supplied proofs are verified and provider effects remain external' hints at behavior but gives no actionable selection criteria.

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