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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, yet the description still adds material context: it is deterministic with no model calls, caller-supplied records are unverified, receipt verification is not supported, and a pass confers no execution authority. Those last two points actively prevent an agent from over-trusting a positive result.

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 short sentences, each carrying new information: capability first, then determinism, then the trust caveat, then the authority limit. No filler and the most decision-relevant constraint (no execution authority) is placed last for emphasis without burying the lead.

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?

Behavioral and trust context is strong, and with no output schema the description is not obliged to explain return values. But for a tool with six parameters, nested objects, two enums and zero schema coverage, the complete silence on verify/version/policy leaves real gaps an agent would have to guess through.

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% across six parameters, so the description must carry the semantics and largely does not. It hints at reply vs batch cases and at 'supplied outcome records' for record, but says nothing about policy structure, and completely ignores verify and version, whose enums ('optional'/'required') matter for calling correctly. Worse, 'receipt verification is unavailable here' sits awkwardly against a verify parameter that accepts 'required', leaving the agent unsure which governs.

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?

Names a specific verb (check) and resource (one reply or up to 50 replies/batch cases) and states the criteria it evaluates against: explicit prices, forbidden phrases, supplied outcome records. It implicitly separates itself from verify_bundle by declaring receipt verification unavailable here, but never mentions validate_policy, so sibling differentiation is partial rather than explicit.

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?

Scope is implied clearly (single reply or batch of up to 50, deterministic, no model calls), which tells the agent when this fits. However, there is no explicit guidance on when to choose policy_check rather than validate_policy or verify_bundle, and no prerequisites or exclusions beyond the verification note.

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