Compliance Check

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

The description discloses the concrete endpoint (POST /v1/compliance/check) and a hard cost (1.00 USD x402 on eip155:8453), which is genuinely valuable decision context beyond the annotations. However, annotations declare readOnlyHint=false and openWorldHint=true, and the description never explains what side effect or external state makes this a non-read operation, nor what the paid call returns.

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?

It is short, but the brevity comes from under-specification rather than economy: the first line merely repeats the title and the second is boilerplate route/pricing metadata. No sentence conveys the tool's actual job.

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?

An output schema exists so return values need not be spelled out, but with nine undocumented inputs, an unexplained non-read-only side effect, and an opaque purpose, the definition is far short of what an agent needs to invoke this 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?

Nine parameters with 0% schema description coverage, and the description mentions none of them. Fields like users, sector, data_types, and custom_details carry no explanation of format or expected values anywhere.

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 is essentially the title 'Compliance Check' restated, plus a transport route and price. It never says what is being checked, against which framework, or what the output represents, so it cannot be distinguished from siblings like v1_policy_check, v1_mandate_compliance, or v1_bio_compliance_query.

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?

There is no guidance on when to use this tool, what preconditions apply, or which of the many compliance/policy siblings it replaces. An agent has no basis for selection other than the word 'compliance'.

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