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

With no annotations, the description must fully disclose behavioral traits. It mentions 'deep-compare' but does not explain how it handles nested structures, array order, type differences, or whether it modifies anything. Critical details like performance, edge cases, and output behavior are missing.

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 of nine words, highly concise. It conveys the core purpose without waste, but could be slightly front-loaded with more critical detail. Still, it is appropriately sized for a straightforward tool.

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 performing deep comparison with no output schema, the description is too brief. It does not explain the output format (list of paths), return type, error handling, or behavior with invalid inputs. Given the complexity and lack of annotations, more detail is needed.

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 description coverage is 0%, so the description must add meaning to parameters. It describes parameters as 'two JSON documents' but does not clarify that they are JSON strings, object representations, or valid JSON inputs. The schema only specifies 'string', lacking format constraints. Minimal value added.

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 function: deep-compare two JSON documents and list differing paths. It uses specific verbs and resource, and distinguishes from siblings that might not list paths explicitly, though it could be more precise about the output format.

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 vs. alternatives like json_pretty_diff or json_validate. The description lacks context on prerequisites, limitations, or use cases, leaving the agent with no decision support.

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