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

With no annotations present, the description carries the behavioral transparency burden. It discloses a useful trait—the body is discarded—but it does not state what the tool returns, whether it is strictly read-only, or how invalid JSON is surfaced. This is a meaningful gap for a validation tool.

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 the primary purpose first and a useful behavioral note second. Every word contributes, and there is no redundant restating of the tool name.

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?

Although the stated purpose is simple, the schema has seven input fields and no output schema. The description does not identify which field carries the JSON body, whether fields are required or mutually exclusive, or what a caller should expect as a result. An agent cannot confidently invoke it correctly without additional information.

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, so the baseline is 3. The description adds little beyond saying the body is discarded, and it does not clarify how the 'body' relates to the several parameters, especially 'json'.

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 a specific action and resource: 'Check whether a body is valid JSON.' This distinguishes it from sibling shape/validation tools that target URLs, paths, keys, or titles. However, the term 'body' is not explicitly mapped to the 'json' input parameter, leaving minor ambiguity about what exactly should be passed.

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 description implies the tool is for validating JSON, but it gives no guidance about when to prefer this over sibling validators, nor does it mention exclusions or alternatives. It is adequate as an implied usage statement but does not actively route the agent.

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