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

With no annotations, the description carries the transparency burden. It usefully discloses that the body is discarded, indicating a non-persistent check, but it does not explain return values, validation failure behavior, or size/format limits.

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, front-loads the core purpose, and avoids filler. The second sentence adds a meaningful behavioral note about disposal, so no sentence is wasted.

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 definition is incomplete for a tool with no output schema and a seven-property input schema. It does not say which parameter carries the JSON, what a valid result looks like, or what happens on invalid input, leaving an agent to infer critical calling details.

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 has property descriptions for every parameter, so schematically this is well covered. The tool description adds no parameter-level meaning and its use of 'body' does not map cleanly to the schema's 'json' field, but the schema already documents 'JSON text to validate; discarded after the check.'

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 states a clear verb and resource: 'Check whether a body is valid JSON.' It distinguishes the tool as a JSON validation action, though it does not differentiate from sibling validation tools like domain-shape or file-path-ok, and 'body' is not mapped to a stated parameter.

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 usage guidance is provided. The description does not explain when to use validate-json instead of sibling tools such as normalize-url, domain-shape, or fetch-status, nor does it mention exclusions or prerequisites.

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