json_tool

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It lists operations but does not explain side effects (e.g., whether set/delete/merge modify files in place), return values, or error handling. The mention of 'deep/shallow/replace' for merge hints at behavior but is insufficient for a tool that likely performs mutations.

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 two sentences with no filler. It front-loads the core purpose and then provides a compact list of operations, making it highly scannable and efficient for an agent to parse.

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 tool's complexity (10 parameters, no output schema, no annotations), the description is incomplete. It does not explain how parameters relate to each operation (e.g., diff requires compareTo, merge uses mergeWith/mergeWithFile, transform uses transforms), nor does it describe return values or expected file behavior. Valuable operational context is missing.

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 100%, providing baseline 3. The description adds meaningful context by giving JSONPath syntax examples ($.key, $..key, $.arr[*]) and explicitly noting merge strategies (deep/shallow/replace), which helps clarify the 'strategy' parameter and the nature of operations beyond the schema's terse descriptions.

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 performs 'Deep JSON operations' and lists specific operations (get, set, delete, merge, diff, flatten, unflatten, validate). This specific verb+resource phrasing distinguishes it from generic siblings like process_tool or yaml_tool, making its purpose unmistakable.

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 implies JSON manipulation as the core use case, but it does not explicitly state when to choose this tool over alternatives (e.g., yaml_tool for YAML, diff_tool for diffing). There are no exclusions or alternative recommendations, so guidance is limited to implied context.

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