ag_json_path_extract

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

With no annotations provided, the description carries full responsibility for behavior disclosure. It covers determinism, missing-path handling, authentication/rate limits, and the return of a provenance envelope, giving a thorough picture of expected 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?

The first two paragraphs largely repeat the same information ('Extract values...' and 'Extracts values...'), adding unnecessary redundancy. While the description is not excessively long, it could be tightened without losing meaning.

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?

The description includes enough context for effective use: payload schema, path format, return behavior, error handling, determinism, authentication, and rate limits. It also provides the output schema, making it self-contained for an 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 explains the payload must contain 'value' and 'paths' via an embedded schema, and clarifies path syntax with examples. It also indicates api_key is for member budget access, though it does not deeply detail the api_key parameter itself or the exact output array structure beyond 'results'.

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 values at dotted/indexed paths from a JSON value, with a specific verb and resource. It also distinguishes itself from asking a model to read a field, making its purpose unambiguous even among many sibling tools.

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?

It explicitly mentions being cheaper and stricter than asking a model, which provides a usage alternative. It also describes return semantics (found/not-found) and error behavior (never throws on missing path), giving clear guidance on when to use it.

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