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 only mentions that the body is discarded, omitting important context such as no disk access for 'path' or no network for 'url', which are hinted in parameter descriptions but not in the tool description. No side effects, permissions, or safety profile are disclosed.

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 sentence, but it is under-specified rather than concise. For a tool with 9 parameters and no annotations, this is too terse and omits essential context, making it inefficient for an agent to parse useful intent.

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 severely incomplete for a tool with 9 parameters, no annotations, and no output schema. It does not explain what the tool actually validates, what inputs are expected, or what the result will be. An agent cannot determine when to call this tool or what it returns, making it nearly unusable.

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 schema provides full descriptions for all 9 parameters, so the tool description is not required to repeat them. However, it adds no additional meaning about how parameters relate to the validation or which are essential, leaving the agent to infer the tool's actual purpose from the parameter list alone.

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 says 'Check whether a body is valid JSON' but 'body' is undefined and the tool's actual scope (which of the 9 parameters are relevant) is unclear. It is essentially a restatement of the name 'validate-json' and does not distinguish the tool from sibling shape-checking tools like 'domain-shape' or 'file-path-ok'.

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 versus alternatives. The only additional note, 'The body is discarded,' is a behavioral trait, not usage guidance. An agent gets no information about conditions, prerequisites, or exclusions.

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