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

Annotations already provide read-only, idempotent, and non-destructive hints. The description adds valuable behavioral context: the operation requires an explicit bounded field map, produces a reversible change report, and costs $1.00 USDC via x402. No contradiction with annotations.

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?

The description is concise and front-loaded, consisting of two sentences with no redundant words. It efficiently states the core action, output, and pricing information.

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 the open-ended input schema and no output schema, the description is the primary source of guidance. It explains the output but leaves the exact input structure (e.g., how the field map is specified) vague. For a tool with potentially complex inputs, this is a notable gap.

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?

The input schema defines no parameters (just an object with maxProperties and additionalProperties). The description adds meaning by indicating the input likely includes a field map and JSON records, which is helpful but not fully detailed. Since there are 0 parameters, baseline is 4 and the description contributes some value.

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 clearly states the action (apply), the resource (JSON records), and the output (transformed data plus a reversible change report). It differentiates from siblings like 'document-transformation' by emphasizing 'explicit, bounded field map' and 'reversible change report', which are distinctive.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for transforming JSON records with a bounded field map, but it does not mention when not to use it or name alternative tools for similar purposes.

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