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

The description contradicts the annotations. Annotations mark openWorldHint=true (external access) but description says 'no external research or outbound actions'. Also destructiveHint=true conflicts with the description's non-destructive 'returns a draft' behavior. While it transparently states price and payment authorization, these contradictions seriously undermine behavioral clarity.

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 brief and front-loaded with the core purpose. It includes necessary operational details (price, payment authorization) without excessive fluff. The structure is efficient, though the pricing/payment info could be more integrated.

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 tool has a nested input object and several signature/idempotency parameters, but the description explains none of them. It lacks any mention of required vs optional fields, how to construct the input, or what the output draft looks like. Given the complexity, this is insufficient for an agent to call it correctly.

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 provides no explanation of any parameters (input object, result_expires, idempotency_key, result_signature, payment_signature). The description does not add meaning beyond the schema fields, leaving agents to guess how to populate them correctly.

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 a specific verb ('Review') and resource ('supplied schema/sample rows'), and specifies the outcome ('propose specific validation rules and correction actions'). This distinguishes it from sibling tools like tradepilot_service_schema_suggestions, which focuses on schema changes rather than quality review.

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 provides some context: it uses only buyer-supplied information, no external research, and returns a draft for human review. However, it does not explicitly mention alternatives or conditions for when to use this tool over others. The absence of explicit comparisons leaves usage guidance implicit.

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