json_query

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

Discloses supported query features (property access, array indexing, wildcards, recursive descent, filters) and return behavior. With no annotations, the description carries the full burden; it covers key traits but omits error handling or timeout behavior.

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 no wasted words. Front-loaded with the primary purpose and immediately provides actionable details on query syntax and use case.

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 no output schema, the description states that it returns matching values as JSON. For a 4-parameter tool with a query language, it covers the main aspects but could benefit from mentioning return format structure or potential errors.

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?

Adds value beyond the schema by providing examples for the query parameter and explaining the alternative input methods (url vs json). The limit is briefly described. Schema coverage is 100%, but the description enhances understanding of usage.

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 verb (fetch/query), the resource (JSON from URL or raw JSON), and distinguishes from siblings like csv_query and regex_extract by specifying JSONPath-lite querying.

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?

Explicitly recommends using this tool instead of loading large JSON payloads into context, providing a clear usage context. However, it does not explicitly state when not to use it or list alternatives beyond the sibling set.

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