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

With no annotations provided, the description carries the full burden of disclosing behavior. It only mentions that the body is discarded, but fails to state what the tool returns (e.g., boolean, error), whether it throws exceptions, or any side effects. The behavior is opaque.

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 concise (two short sentences) and front-loads the main purpose. However, it is under-specified rather than appropriately concise, and the second sentence about discarding the body adds little value without clarity on what 'body' means.

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 9 parameters, no output schema, and no annotations. The description provides almost no information about how to call it, which parameter holds the JSON, what the return value is, or any edge cases. This is grossly insufficient for an agent to use 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 input schema has 100% description coverage for all 9 parameters, so the baseline is 3. The tool description adds no parameter-level meaning and actually introduces confusion by referring to a 'body' that does not exist as a parameter, but since the schema is complete, the baseline holds.

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 clear action (check validity) and a resource (body), but the term 'body' is vague and doesn't match the actual 'json' parameter. It does not differentiate this tool from siblings like 'domain-shape' or 'file-path-ok' that also validate formats, so it lacks specificity.

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. There is no mention of context, exclusions, or selection criteria. The description is a single sentence with no usage hints.

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