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

The annotations already establish that this is a write operation ('readOnlyHint: false') and that it is idempotent. The description adds functional context—the act of matching a saved order against the provider—which is helpful, but it doesn't add technical behavioral traits like rate limits or specific error modes beyond the hint.

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 definition is perfectly sized for its task. It is front-loaded, concise, and avoids any superfluous phrasing, making it immediately clear to the agent.

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 the extremely minimal input schema (1 parameter, 0% coverage), the description provides a necessary functional context. It defines the goal of the tool well enough for an agent to decide if it's the correct tool to satisfy a user request about payment matching.

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?

Since schema description coverage is 0%, the description's job is crucial. It adds meaning by clarifying that 'order_id' refers to a 'saved order,' but it does not elaborate on the required format of the ID beyond what is stated in the schema.

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 clearly defines the action ('Reconcile') and the specific objects involved ('saved order' and 'actual payment provider'). It distinguishes itself from read-only tools like 'get_order' or 'get_proof' by implying a data matching or state-changing operation.

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 tool lacks guidance on when to call it. It does not specify the required preceding steps, such as calling 'checkout' or 'create_payment_link', nor does it distinguish its role within the overall payment lifecycle.

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