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

There are no annotations, so the description must carry the burden of behavioral disclosure. It does disclose that 'the body is discarded,' indicating the input is not persisted or reused. It does not mention return behavior, error handling, or any other side effects, so the disclosure is only partial.

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 one terse sentence that front-loads the purpose and includes the key behavioral note about discarding the body. Every word earns its place; there is no redundancy or filler.

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 seven input parameters, no annotations, and no output schema. The description fails to indicate which parameter is the 'body' to validate and does not explain what the caller receives (boolean, response, exception, etc.). Even though the schema is well described, this ambiguity and missing return information make the definition incomplete for reliable invocation.

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 itself gives detailed descriptions for every property, including `json` ('JSON text to validate; discarded after the check'), so schema coverage is high and the baseline is 3. The description adds no parameter-level detail and instead uses the ambiguous term 'body' without mapping it to a schema property.

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 uses a specific verb ('Check') and a clear object (whether a body is valid JSON), so an agent knows the tool's core function. However, it does not explicitly tie the generic 'body' to the `json` parameter in the schema, leaving mild ambiguity. It stands apart from sibling shape-validators because it is the only one focused on JSON validity.

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 purpose implies the use case: validate whether a given body is valid JSON. But the description gives no explicit when-to-use/when-not-to-use guidance and names no alternatives among the many sibling validation tools, so an agent must infer when this tool is the right choice.

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