read_file_content

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

With no annotations, the description carries the full burden of behavioral disclosure. It states 'directly read' which hints at no transformation, but it does not disclose error handling (e.g., file not found), permissions, encoding, or return format. This is minimal behavioral transparency.

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 a single, front-loaded sentence that efficiently states the tool's purpose. Every word earns its place, with no wasted tokens.

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 absence of annotations and output schema, the description is too sparse. It does not cover when to use it versus siblings, error scenarios, or what the return value looks like. While the tool is simple, this is not enough for an agent to use it with full confidence.

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 one parameter, file_path, covered at 0%. The description adds only 'local file,' providing some context that file_path is a local filesystem path, but it does not explain formats, absolute vs. relative paths, or other semantics. It does not compensate for the lack of schema description.

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 uses the specific verb 'read' and resource 'local file,' clearly stating that it returns content. It distinguishes itself from siblings like list_files_in_directory (listing) and query_local_file (querying) by emphasizing 'directly read the content.'

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: use this when you want to read raw local file content. However, it does not explicitly mention when not to use it or provide alternatives, such as query_local_file or search_local_docs, so it only provides implied guidance.

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