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

The description goes well beyond the annotations by disclosing parser limitations (semicolon/tab input is not detected), required CSV structure, JSON-to-CSV key union behavior, missing-value handling, the returned fields, and the 500,000-character limit. This is rich, actionable behavioral context.

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 compact and front-loaded with the primary purpose, followed by necessary format constraints and return information. Every sentence adds value, and there is no redundant repetition of the schema.

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 two-parameter conversion tool with no output schema, the description covers input requirements, both conversion directions, parsing edge cases, return values, and size limits. An agent has everything needed to select and invoke the tool correctly.

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 schema already covers both parameters at 100%, so the baseline is 3. The description adds meaningful constraints and format details for both 'direction' values and for the 'data' parameter, such as the need for a header row and the array-of-objects requirement for JSON.

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 names the exact operation ('Converts CSV text to JSON or JSON to CSV'), the direction parameter values, and the inline-data scope. This is specific enough for an agent to know exactly what the tool does and to distinguish it from unrelated sibling utilities.

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 clearly states that data must be passed inline and defines the accepted CSV and JSON shapes. It does not explicitly name alternative tools, but it provides enough context about when to use this tool and what input formats are required.

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