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

The description discloses that the body is discarded, which is a behavioral note. However, it does not mention side effects, return values, error handling, or whether extra parameters are ignored. Without annotations to supplement, this transparency is insufficient.

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 and front-loaded with the main purpose, but it is overly terse relative to the complexity of the tool. It omits critical details about inputs and outputs, so while the structure is not bloated, it sacrifices necessary information for brevity.

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?

Given the 9 optional parameters and no output schema, the description is severely incomplete. It does not explain what constitutes a valid JSON body, how the other parameters are handled, what the result format is, or any edge cases. The tool description should have provided far more context to be usable.

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 description mentions a 'body' but the schema has nine parameters, with no indication that 'json' is the actual input. It fails to clarify the purpose of the other parameters, and the schema descriptions (e.g., 'Git ref name; discarded after the shape check') are confusing. The tool description does not reconcile these inconsistencies or add meaningful parameter context.

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 primary action (checking if a body is valid JSON) and mentions that the body is discarded. However, it uses the term 'body' rather than referencing the actual schema parameter 'json', and it does not specify what the tool returns (e.g., a boolean or error), which slightly reduces clarity.

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 description provides no guidance on when to use this tool versus alternatives (such as other validation tools) or when not to use it. There is no mention of context, prerequisites, or example scenarios, so the agent receives no situational direction.

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