complete_preauth

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

No annotations are provided, so the description must disclose behavioral traits, but 'Complete/capture a pre-authorized order' is purely declarative. It does not explain whether this triggers an actual charge, if it is idempotent, requires specific permissions, or what side effects occur.

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 short sentence that immediately communicates the core action. There is no unnecessary information or repetition, making it highly concise and front-loaded.

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 financial tool with no output schema and no annotations, the description is far from complete. It does not address return values, idempotency, whether the capture amount can differ from the authorized amount, or any conditions that must be met. The tool's simplicity does not excuse this lack of essential operational context.

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?

The input schema covers both parameters fully (order_id and amount) with descriptions, so schema coverage is 100%. The description adds no additional meaning beyond what the schema already provides, matching the baseline for well-documented parameters.

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 states the tool's function with a specific verb and resource: 'Complete/capture a pre-authorized order.' This distinguishes it from siblings like 'preauth_order' (which presumably creates the pre-authorization) and 'create_order' (used for orders without a pre-auth).

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 description implies this tool is for finalizing pre-authorized orders but provides no explicit guidance on when to use it vs. alternatives. There is no mention of prerequisites, exclusions, or scenarios where other tools like 'refund_order' or 'preauth_order' would be more appropriate.

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