query_customs_declare

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

With no annotations, the description must disclose behavior. It states this is an inquiry (implying read-only) and provides constraints on request IDs. It does not explicitly confirm non-mutating behavior or describe error handling, but the inquiry nature is clear. This is adequate but lacks depth.

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 relatively short and front-loaded with purpose, followed by parameter details. The 'Args:' section is useful and not redundant. There is minor awkwardness in the first sentence but overall it is efficient.

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 single-parameter query tool with an output schema, the description covers purpose, usage context, and parameter constraints. It does not discuss alternative tools, but that is not required for completeness of the tool's own operation. The presence of an output schema means return values are already specified.

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 schema only specifies an array of strings, but the description explains the IDs are merchant-assigned declaration request IDs, unique, with a maximum length of 64 characters and maximum 10 elements. This fully compensates for the 0% schema description coverage.

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: 'inquire about the status of declared payments' for the Acquiring Service Provider. The verb 'inquire' and resource 'declared payments' are specific, and the tool name query_customs_declare distinguishes it from sibling tools like create_payment or customs_declare.

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 usage when needing to inquire about the status of declared payments, which is distinct from sibling tools like query_payment for regular payments. However, it does not explicitly state when not to use it or mention alternatives, so it misses the highest bar.

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