flatten_nested_json_object

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

With no annotations, the description carries the burden and adds meaningful behavior: it discloses recursion-depth safety limits that prevent memory crashes and states the monetary cost (0.005 USDC on Base L2). It stops short of specifying the exact depth limit or failure mode when that limit is exceeded.

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?

A single front-loaded sentence communicates the operation, output format, safety behavior, and cost with no redundancy. Every element earns its place.

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 transformation tool, the description covers the input shape, output keys, safety mechanism, and payment requirement; without an output schema, it still tells the agent the return style. Minor gaps remain around exact depth-limit behavior and paymentSignature enforcement.

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 100%, so the schema already documents both payload and paymentSignature. The description adds general context about nested JSON and dot-notation output but does not explain the parameters beyond what the schema states.

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 uses a specific verb+resource ('Flattens deep nested JSON hierarchies') and specifies the output convention ('dot-notation keys'), making the tool's job unmistakable. It also distinguishes this from JSON-adjacent siblings such as repair_malformed_json or minify_json_schema.

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 use case is implied by the description: use when a nested JSON object must be flattened into dot-notation. However, it does not explicitly state when to prefer this tool over related JSON tools, list exclusions, or provide workflow context.

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