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

The description says 'the body is discarded,' which discloses an important non-retention behavior. Since no annotations are provided, this helps but does not fully cover other behavioral aspects such as return behavior, side effects, or error handling.

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 extremely concise: two short sentences with no filler. The core purpose is front-loaded, and the behavioral note about discarding earns its place.

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?

The tool has no annotations and no output schema, so the description should explain enough about the call contract, including what is returned. It does not state the output format or how validity is reported, leaving an important gap for an agent that needs to act on the result.

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 already provides descriptions for all parameters, including 'JSON text to validate.' The description adds no additional parameter-level meaning beyond what the schema communicates, so the baseline score of 3 is appropriate.

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 validates whether a body is valid JSON, with a specific verb and resource. It does not explicitly distinguish itself from the sibling shape-validation tools, but the focus on JSON is enough to make the core purpose unambiguous.

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: call this tool when you need to check whether a body or JSON text is valid JSON. However, there is no explicit guidance about when not to use it or which alternative tool to prefer, so the usage guidance is only implicit.

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