read_file

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool reads and returns file content, which implies a read-only operation, but doesn't mention permissions needed, rate limits, file size limitations, or error conditions. The description adds basic context but lacks important behavioral details for a file access tool.

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 perfectly structured with a clear purpose statement followed by parameter explanations. Every sentence earns its place: the first sentence states the core functionality, and the parameter descriptions are essential for understanding usage. No wasted words or redundancy.

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 moderate complexity (file reading with truncation), no annotations, and the existence of an output schema (which handles return value documentation), the description is reasonably complete. It covers the purpose and parameters well, though it could benefit from more behavioral context about limitations or error handling.

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?

With 0% schema description coverage, the description must compensate for the schema's lack of parameter documentation. It provides meaningful explanations for both parameters: 'file_path' as 'Full path to the file in Dropbox' and 'max_length' as 'Maximum characters to return (0 for no limit)', which adds substantial value beyond the bare 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?

The description clearly states the specific action ('Read and return the full content') and the resource ('a file'), distinguishing it from siblings like get_file_info (metadata), list_files (directory listing), and search_file_content/search_files (search operations). The verb+resource combination is precise and unambiguous.

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 implies usage for reading file content, but doesn't explicitly state when to use this tool versus alternatives like get_file_info (for metadata) or search_file_content (for searching within files). It provides clear context for reading full content, but lacks explicit exclusions or named alternatives.

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