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

The description discloses a key behavioral trait: 'The body is discarded.' With no annotations provided, it takes on the burden of transparency, but it does not describe the return value (boolean vs. error) or how other input parameters are treated beyond the schema descriptions. It adds some value but leaves important behavioral details to the schema.

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?

Two sentences with zero filler: first states purpose, second states the discard behavior. Every word earns its place and the most important information is front-loaded.

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 a large schema with many unrelated parameters, but the description doesn't clarify that only 'json' is used and others are ignored/discarded. The term 'body' is inconsistent with the actual parameter name 'json', which could confuse an agent about required inputs. No output schema or additional context is provided to fill the 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 schema descriptions already cover all parameters, including the key 'json' field. The tool description adds no new parameter-level semantics, and the word 'body' doesn't map directly to any schema property. Baseline of 3 is appropriate given the high schema description coverage.

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?

States a specific verb and resource ('Check whether a body is valid JSON') that clearly differentiates it from sibling shape/URL validators. The purpose is immediately unambiguous even without reading the schema.

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 use this tool over alternatives, and no explicit exclusions or prerequisites. The only contextual signal is the obvious implication that it is for JSON validation, which doesn't help an agent decide among sibling tools.

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