read_data

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

Discloses different modes for .mat files (summary vs raw) and behavior for text files, but does not detail behavior for other file types like .csv or .xlsx. With no annotations, description carries the burden and does well.

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?

Two sentences, front-loaded with purpose, no wasted words.

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?

Describes key behaviors and file types, but could be more thorough on error conditions or file size limits. Output schema exists, so return details are not needed.

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?

Adds context for the 'format' parameter (summary/raw for .mat) and specifies default and raw mode returns base64, but leaves behavior for 'format' with non-.mat files unclear. Schema coverage is 0%, so description partially compensates.

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?

Clearly states it reads data files of specific types (.mat, .csv, .json, .txt, .xlsx) from the session temp directory, distinguishing it from siblings like read_image and read_script.

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?

Implies usage for reading data files from the session temp directory but does not explicitly state when to use versus alternatives or provide exclusions.

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