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

There are no annotations, so the description carries the full burden. It usefully discloses that the body is discarded, implying no data retention, but it does not explain the return value, whether invalid JSON produces an error or a false result, or how strict validation is.

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 short sentences with no wasted words; the purpose is front-loaded and the disposal behavior is stated immediately. The description is concise and to the point.

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 9 optional parameters, no output schema, and no annotations, this description is too minimal. It does not state which parameter represents the JSON body, what a successful or failed validation looks like, or whether the tool returns a boolean, a report, or an error. These gaps make it incomplete for safe autonomous 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?

Schema coverage is 100%, so the parameters are already documented and the description need not repeat them. The description adds only the vague term 'body' while the schema clearly identifies the 'json' parameter as the JSON text to validate, but it does not clarify which of the 9 optional parameters should be provided.

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: checking whether a body is valid JSON. It is clearly distinct from sibling shape-checking tools like domain-shape or jira-key-shape, though it does not name an alternative.

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 given about when to use validate-json versus sibling shape-check tools, and no exclusions or conditions are mentioned. The description only defines what the tool does, not when it should be selected.

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