company_reconcile_bank

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

No annotations are present, so the description carries the full burden. It does disclose two behavioral traits: supplied proofs are verified and provider effects remain external. However, it leaves side-effect scope, reversibility, and prerequisites ambiguous, which is significant for a tool that can 'advance' a lifecycle.

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 front-loaded sentence with no filler; each clause adds a distinct idea: inspect/advance, lifecycle scoping, proof verification, and external effects. While compact, the density makes it somewhat cryptic rather than fully clarifying.

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?

With seven parameters, no annotations, and 0% schema coverage, the description is far from sufficient for an agent to construct a valid invocation. The output schema covers return values, but the lifecycle model, required bundle format, and operation semantics remain unspecified, leaving too much to inference.

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 none of the seven parameters are documented in the schema. The description only hints that 'supplied proofs' relate to the required bundle_json and that operation may toggle between inspect and advance, but it fails to explain project_id, entity_ref, payload_json, now, or engine.

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 specific resource ('reconcile bank') and a dual action ('Inspect or advance') tied to a lifecycle, which goes beyond a tautology. However, the meaning of 'reconcile bank', its 'scoped lifecycle', and the concrete outcomes are left undefined, and there is no differentiation from sibling tools like company_bank or finance_xero_bank_reconciliation.

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 siblings or when to choose 'inspect' versus 'advance'. There are no alternatives, exclusions, prerequisites, or contextual conditions, so an agent cannot determine selection criteria from the description.

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