json_json_get

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

With no annotations, the description takes on the burden. It explains path syntax, wildcard behavior returning a list, and the return type as a JSON string. However, it does not disclose error handling on invalid JSON or paths.

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?

Two sentences with examples, no filler. Front-loaded with the purpose, then examples, then return type. Efficient and well-structured.

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 simplicity (2 params, no annotations, output schema exists), the description is mostly complete. It covers path usage, return format, and wildcard. Lacks explicit statement about data being a valid JSON string, but that is inferred.

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 coverage is 0%, so the description must add meaning. It explains the 'path' parameter with examples and mentions wildcard usage. It does not explicitly describe the 'data' parameter as a JSON string, but the schema type 'string' is clear.

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 extracts a value from JSON using dot-notation path, with specific examples. It differentiates from siblings like json_json_filter and json_json_set, which have different purposes.

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 usage by providing examples but does not explicitly state when to use this tool over alternatives like json_json_filter for complex queries or json_json_get for simple extraction. No when-not-to-use guidance is given.

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