data_to_json

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

No annotations are provided, so the description carries the full burden. It discloses the output shape ('pretty JSON string') and implicitly flags failure on non-serializable input via the qualifier 'JSON-serializable', but says nothing about error behavior, key ordering, or whether it is a pure/side-effect-free operation.

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 with no filler; the essential purpose and output form arrive immediately.

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?

An output schema exists, so return-value explanation is unnecessary, and the tool is simple with only two parameters. The main remaining gap is the unstated semantics of 'indent' and any error behavior for non-serializable input.

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 0%, and the 'data' parameter has no type at all in the schema; the description partially compensates by clarifying it accepts 'any JSON-serializable data'. However, the 'indent' parameter is never mentioned in either the schema or the description, so its formatting effects must be inferred from the default of 2 and the word 'pretty'.

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?

States a specific verb ('Serialize') and both the input class ('any JSON-serializable data') and output form ('pretty JSON string'). It is distinguishable from siblings like data_read_json or data_flatten_json, though it does not explicitly name how it differs from them.

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?

No guidance on when to use this versus data_flatten_json or data_read_json, and no prerequisites or exclusions. The agent must infer applicability purely from the one-line purpose statement.

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