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

With no annotations, the description carries the full burden and does disclose two useful traits: it is a paid tool at $0.04 USDC and it stops short of jurisdiction-specific legal conclusions. However, it says nothing about return format, idempotency, or how the x402 payment flow behaves beyond what the schema already states.

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?

A single front-loaded sentence with the cost first and the scope caveat second; nothing is wasted. It is efficient, though it could carry slightly more substance for a paid tool.

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?

No output schema exists, so the description is the only place to explain what the extraction returns, and it does not. It covers the paid nature and the legal-conclusion boundary but leaves the shape of the result and the payment retry flow to the schema.

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%, so all four parameters including the required 'text' and the paymentSignature flow are already documented in the schema. The description adds no parameter-level meaning, so the baseline 3 applies.

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+resource ('extracts employment terms') and adds a meaningful scope boundary ('without making jurisdiction-specific legal conclusions'). The resource is distinct enough from siblings like extract_payment_terms or extract_renewal_deadline, though no sibling is named explicitly.

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 guidance on when to use this versus the many alternative extraction and analysis tools (analyze_contract_risk, extract_contract_obligations, etc.). Usage is only implied by the resource name; no conditions, prerequisites, or exclusions are given.

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