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

With no annotations provided, the description carries the transparency burden. It explicitly discloses that 'The body is discarded,' signaling a read-only, no-persistence behavior. It does not describe error handling or response format, but for a simple validity check the disposal behavior is a meaningful transparency disclosure.

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 no filler. It front-loads the core purpose and then adds the key behavioral note about discarding the body. Every word earns its place.

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 description is adequate for a simple validation tool, but the tool has 9 parameters, no annotations, and no output schema. It does not explicitly identify which parameter receives the JSON or describe what the tool returns. The many unrelated schema parameters also create potential confusion, so the description alone is not fully complete.

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?

Schema description coverage is 100%, so the schema already documents every parameter. The description adds no parameter-level meaning beyond the schema. The json parameter is clearly labeled in the schema, but the description's 'body' phrasing leaves the mapping from description to parameter slightly indirect.

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 specific action and resource: 'Check whether a body is valid JSON.' This clearly distinguishes validate-json from sibling tools like browser-url-ok, file-path-ok, and domain-shape, which validate different kinds of inputs.

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 when to use the tool: when a JSON body needs validation. However, it gives no explicit guidance on when not to use it or which sibling tools to prefer for non-JSON shape checks. The usage context is implied rather than stated.

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