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

The description contradicts the annotations. Annotations mark openWorldHint=true and destructiveHint=true, but the description claims 'no external research or outbound actions.' Payment and wallet authorization are themselves outbound side effects, so this blanket claim is misleading.

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?

Four concise sentences, with the core action front-loaded. Each sentence adds a distinct constraint or expectation: output behavior, input scope, review status, and pricing/authorization. No wasted words.

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?

The description covers high-level behavior and pricing, but with no output schema and five parameters, it omits essential invocation details like idempotency, result expiration, signature requirements, and exact return structure. An agent would struggle to call this correctly without additional documentation.

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 explain the brief, audience, result_expires, idempotency_key, result_signature, or payment_signature parameters. It only loosely implies the source_text input via 'supplied text.' Given five parameters and no schema descriptions, this is a critical gap.

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 states a specific verb and resource: extract tables from supplied text into a structured representation. It also adds concrete output expectations—preserve values and flag ambiguous cells—which clearly distinguishes this from generic extraction or other text-processing siblings.

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?

It implies when to use it: when you have buyer-supplied text containing tables and want a review-ready draft. It does not explicitly name alternatives or exclusion criteria, such as when to choose csv_table_convert or invoice_text_extraction instead.

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