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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), and the description adds genuinely new behavioral context: the call is metered (0.05 USDC), requires an X-Bazaar-Key header, and a free sample report is available at a URL. It does not describe latency, failure behavior, or what the composite report contains.

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?

Pricing and auth are front-loaded, followed by the check list and a sample link, with no filler sentences. The check enumeration is a dense run-on rather than a clean list, costing one point.

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?

Given a six-check composite with no output schema and only one input parameter, the description leaves notable gaps: it never says what the returned report looks like, whether findings are aggregated into a pass/fail, and why only a single amount parameter suffices. It is adequate to decide whether to pay and call, but thin for interpreting the result.

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?

There is a single parameter with 100% schema description coverage ('Transaction amount in USDC'), so the schema already carries parameter meaning and the baseline of 3 applies. The description adds no clarification of how amount_usdc relates to the call, and the '0.05 USDC' price could even create mild confusion with the amount parameter.

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+resource ('Composite 6-check crypto compliance & tax audit') and enumerates the six chained checks: OFAC batch screening, Schedule C lint, 1099-DA reconciliation, FIFO/HIFO basis, and quarterly safe harbor. It implicitly distinguishes itself from single-purpose siblings like ofac_check and schedule_c_row_lint by being a chained composite, though it never explicitly says so.

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?

Usage is only implied: the word 'composite' suggests it is for users who want all six checks at once, and the payment line ('Paid x402 / X-Bazaar-Key: 0.05 USDC') gives the precondition for calling. There is no explicit when-to-use vs. when-to-use-a-single-check-tool guidance and no mention of prerequisites or exclusions.

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