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

With no annotations provided, the description reveals a key behavior ('null deletes keys') but omits other important traits such as array replacement behavior, error handling, or the structure of the return value.

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 extremely concise at two sentences, front-loading the core purpose and usage context without any unnecessary information.

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 simple tool with two parameters and no output schema, the description provides minimal but adequate context, though the lack of parameter semantics and return format details leave gaps for an AI agent.

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 does not explain the 'target' and 'patch' parameters beyond their names; with 0% schema description coverage, the agent lacks essential context about what each parameter expects as input (e.g., JSON strings).

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 specifies 'Apply RFC 7396 JSON Merge Patch (null deletes keys)' which clearly states the tool applies a specific JSON merge patch standard, distinguishing it from siblings like json_patch_apply (RFC 6902) and json_merge.

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 advises 'When: RFC 7396 merge patch — use when patching JSON configs', providing clear context for when to use this tool, though it does not explicitly mention when not to use it or alternative tools.

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