sassy_read_file

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

With no annotations, the description carries the behavioral disclosure burden. It clearly explains offset/length semantics, including the tail behavior for negative offset and the fact that length is ignored in that case. It does not mention error cases or permissions, but for a simple read operation, the key behaviors are well-disclosed.

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 extremely concise, front-loading the purpose and then using a compact, readable format for parameter semantics. Every line adds value, with 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?

Given the tool's simplicity, output schema presence, and the well-explained parameters, the description is largely complete. It lacks error handling context and does not address when to use this tool vs alternatives, which slightly detracts. However, for a line-paginated file reader, this covers the essential behavior.

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 description coverage is 0%, so the description must compensate. It does this well for offset and length, explaining the 0-based start, tail mode, and the interaction between length and negative offset. 'path' is left undescribed, but its meaning is obvious from the tool name and 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 states 'Read file contents with line-based pagination,' which is a specific verb+resource. It distinguishes this tool from siblings like sassy_read_multiple and sassy_file_info by highlighting the pagination feature, making the purpose 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?

No guidance is provided about when to choose this tool over sibling file-reading tools. The parameter semantics are explained, but there is no mention of exclusions or alternatives, leaving the selection decision entirely to the agent.

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