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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly says the body is discarded, providing a meaningful non-retention guarantee and implying the operation has no persistent side effects. It does not describe the return value or error behavior, but for a simple validator this is a reasonable level of transparency.

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 two short sentences with no filler. The core action is front-loaded and the important discard behavior is stated immediately afterward.

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?

Despite the simple action, the tool has a nine-parameter schema, no required parameters, and no output schema. The description does not clarify which parameter is the JSON body, what the tool returns, or how the other parameters relate to validation. The schema helps, but the description alone leaves significant operational ambiguity.

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 the schema already documents each parameter. The description itself adds no parameter-level meaning and uses 'body' rather than naming the `json` parameter, though the schema clearly explains that `json` is the text to validate.

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 tool checks whether a body is valid JSON, using a specific verb and resource. It is distinguishable from sibling shape-checking tools, though the term 'body' is somewhat vague and does not map directly to a schema property.

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?

The intended use is implied: use this tool to validate JSON. However, it does not explicitly contrast with sibling tools or state when not to use it, leaving the agent to infer the appropriate selection from the name and description.

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