file_file_read

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

No annotations provided. Description adds truncation behavior for files >32KB, which is helpful. But lacks mention of error handling (e.g., file not found) or performance implications.

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 short, front-loaded sentences: purpose first, then important truncation note. No fluff.

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?

Has output schema (not shown), description covers core behavior and truncation. Lacks error conditions, but for a simple read tool, it's nearly complete.

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 0%, yet description adds no detail about the 'path' parameter (e.g., format, relative vs absolute). Agent gets no extra guidance beyond the schema.

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 'Read a file and return its contents' with a specific verb and resource, distinguishing from sibling tools like file_file_append or file_file_write. Also notes truncation limit.

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?

Implied usage: read a file. No explicit alternatives or when-not-to-use, but the context is clear and no misleading information.

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