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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety and scope profile. The description adds important behavioral context beyond annotations: the tool is paid per call via x402, and it clarifies what the verification checks (product, custody events, recall status, record integrity). It does not detail payment mechanics or error behavior, but the cost disclosure is significant.

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?

Two sentences, front-loaded with the operation and its scope, followed by the payment requirement. No filler or repetition; every clause earns its place.

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 simple read-only tool with one required parameter and no output schema, the description gives a good sense of what is verified and notes the x402 payment model. It stops short of describing the exact return structure or differentiating from sibling tools, but the core context is sufficient for an agent to invoke 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 100% for the single required parameter lot_code, which the schema already describes as 'Lot or batch code to verify.' The description mentions 'a lot' but adds no format, constraints, or validation details beyond the schema. Baseline 3 applies when the schema fully documents 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?

States a specific verb and resource: 'Verify a lot.' It also enumerates the verification scope (product, first/latest custody events, recall status, record history integrity), so the agent knows exactly what operation is performed. However, it does not distinguish this tool from siblings such as privi_chain_of_custody or privi_lookup_fingerprint.

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?

No when-to-use guidance, prerequisites, or alternative tools are mentioned. The description implies usage when a lot code needs verification, but it does not say when to choose this over privi_chain_of_custody, privi_lookup_fingerprint, or the other siblings. 'Paid per call via x402' is a cost notice, not usage guidance.

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