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

With no annotations, the description carries the full burden, but it does disclose a meaningful behavioral trait: this is a paid tool costing $0.04 USDC. That is genuinely useful for an agent deciding whether to invoke it. However, it says nothing about failure modes, what happens if no NDA clauses are found, or output shape.

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 sentence with no waste, and the pricing disclosure is appropriately front-loaded for a paid x402 tool. Slightly dense with the clause enumeration but each item earns its place by telegraphing scope.

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?

There is no output schema and no annotations, so the description should do more work. It partially compensates by listing the clause categories it returns, but omits output format, behavior on missing clauses, and any input length or document-type constraints.

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 (text, title, counterparty, paymentSignature) are already documented in the schema. The description adds no parameter-level detail beyond what is structured, so the baseline of 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?

Names a specific verb (extracts) and resource (NDA clauses), then enumerates the exact clause types covered: confidentiality scope, duration, exclusions, residuals, return/destruction. This distinguishes it from broad siblings like analyze_contract_risk, though the differentiation is implied by the 'NDA' qualifier rather than stated.

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 choose this over extract_contract_obligations or analyze_contract_risk, and no stated prerequisites beyond the implied need for contract text. The agent must infer applicability from the NDA-specific clause list alone.

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