webdev_json_to_csv

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It mentions features like unicode quoting and tab/pipe output, but lacks details on error handling, size limits, or side effects. Some transparency is given but not comprehensive.

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 description is concise, consisting of two sentences plus a menu ID. It front-loads the purpose and is structured logically. Minor improvement could be removing the menu ID for even greater conciseness.

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 complexity (converter with multiple options) and the absence of an output schema or annotations, the description provides a basic overview but not full guidance. It directs users to 'describe_tool' for completeness, which partially mitigates the gap.

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 input schema has no defined parameters (additionalProperties: true), so the description is the only source for parameter meaning. It hints at parameters like custom delimiters and header rows but does not explicitly name or describe them. This adds some value beyond the empty schema but remains vague.

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 converts JSON to CSV with specific features like custom delimiters, header rows, and nested-object flattening. It distinguishes itself from the sibling tool 'webdev_csv_to_json' by specifying the conversion direction.

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 mentions using 'describe_tool' for full guidance, implying additional details elsewhere, but does not explicitly state when to use this tool versus alternatives or when not to use it. Usage context is implied through feature list but not explicit.

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