read_file_advanced

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

The description adds value by mentioning multi-encoding and partial reading support beyond the schema, but it does not disclose error behavior, permissions needed, or potential side effects. With no annotations, the burden on description is higher, yet it remains minimal.

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, short sentence that conveys the core purpose and key differentiators. No unnecessary words; every part earns its place.

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 5 parameters and no output schema or annotations, the description is somewhat lacking. It does not explain return format, error cases, or constraints on parameter combinations. It captures the essence but is not fully 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 100%, so the description does not need to add much. It summarizes parameters (multiple encodings, partial reading) but adds no further semantic meaning beyond what the schema provides.

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 tool is an advanced file reading function supporting multiple encodings and partial reading. It uses a specific verb and resource, and effectively distinguishes itself from the simpler sibling 'read_file'.

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 context of sibling tools implies this is for advanced scenarios, but no explicit when-to-use or when-not-to-use guidance is provided. It is clear but lacks exclusions or alternatives direct comparison.

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