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

The description only says the body is discarded, which is about data retention, not behavioral traits like side effects, permissions, or return values. There are no annotations to supplement. The tool's behavior of returning a boolean or error is not disclosed. It also doesn't mention that it only uses the 'json' parameter.

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, which is concise, but it lacks structure and important details. It's not front-loaded with usage context; it just states the purpose.

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?

For a tool with 9 parameters and no output schema or annotations, the description is severely incomplete. It doesn't explain the return value, which parameter to use, or any limitations. An agent would be uncertain how to call it correctly.

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 descriptions are detailed, but the tool description adds no clarification about which parameters are relevant. With 9 optional parameters, only 'json' seems relevant, but the description doesn't say that. This could lead an agent to populate multiple fields unnecessarily.

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 the tool checks JSON validity, distinguishing it from other shape-check tools. However, the parameter schema is cluttered with unrelated fields, which could confuse an agent about what the tool actually operates on. The verb 'check' and resource 'body' are specific, so it's clear enough.

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 on when to use this tool versus other validation tools. It doesn't mention alternatives or any preconditions. An agent would have no idea when to choose this over, say, file-path-ok or domain-shape.

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