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

With no annotations, the description carries the full burden of behavioral disclosure. It notes that the body is discarded, which is a side effect, but omits the return value, error behavior, and any other operational details. For a validation tool, this is a significant gap.

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 a single, efficient sentence with no unnecessary words. It front-loads the purpose and is appropriately sized for a simple tool.

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?

With no output schema or annotations, the description is expected to thoroughly explain the tool's behavior. It fails to mention the return type (e.g., boolean), behavior on invalid JSON, or the purpose of the other parameters. The tool appears to be a simple validator, yet the description leaves many operational details unclear.

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?

While the schema descriptions cover all parameters at 100%, the description introduces ambiguity by using 'body' instead of the schema's 'json' parameter. Additionally, the schema includes three irrelevant parameters (url, host, zone) that the description does not clarify or justify. The description adds little value beyond the schema and may mislead an agent about which parameter is actually used.

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 (check) and the subject (whether a body is valid JSON). However, it does not differentiate from sibling tools and uses the ambiguous term 'body' instead of the schema's 'json' parameter. The core purpose is still evident, but the differentiation is lacking.

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 is provided on when to use this tool over alternatives like compatibility or domain-shape. The description gives no context about typical use cases, exclusions, or prerequisites, leaving an agent to guess when this is the appropriate choice.

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