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

With no annotations, the description carries the full burden, and it does disclose an important behavioral trait: idempotency, which tells agents that repeated calls are safe. However, it does not clarify whether reconciliation has side effects, what the response looks like, or what prerequisites or permissions are needed.

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 that wastes no words. It places the key behavioral term 'Idempotently' first and conveys the core operation compactly.

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?

For a tool with one simple parameter and no output schema, the description gives a reasonable starting point by stating the operation and the domain. It is incomplete, though, because it leaves usage timing, side effects, and return behavior unspecified, and there are no annotations to fill those gaps.

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%, so the description must compensate for the undocumented `outcome_id` parameter. It only references 'an outcome' generically and never explicitly explains that `outcome_id` is the identifier of the outcome being resumed, nor its format or required semantics.

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 action ('Idempotently poll or reconcile') and a resource ('pending supplier and financial operations for an outcome'), which distinguishes it from the sibling tools that request, get, or confirm outcomes. However, the phrase 'poll or reconcile' is slightly ambiguous about whether these are alternative modes or intertwined steps.

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 word 'pending' implies this tool is for handling outcomes that have unfinished supplier or financial operations, giving some context for when to use it. It does not explicitly say when not to use it or name any alternative, so usage guidance is only implied rather than stated.

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