sassy_session_read

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: it returns only text that arrived since the last read and does not send input. This adds meaningful behavioral context beyond the basic purpose, though it does not mention potential side effects like whether the output is marked as read.

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 two sentences, front-loaded with the primary action, and contains no redundant information. Every word 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?

For a simple one-parameter read tool with an output schema, the description provides sufficient behavioral context to invoke the tool correctly. The only gap is the unstated meaning of 'name', but given the tool's simplicity and sibling context, it is largely 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?

The description does not explain the 'name' parameter at all, and schema coverage is 0%. Since the schema provides no description either, the parameter's meaning must be inferred from the tool name and sibling tools. The description fails to compensate for the lack of documentation.

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's function: 'Read new output from a session without sending input.' It uses a specific verb ('read') and resource ('session output'), and the phrase 'without sending input' distinguishes it from sibling tools like sassy_session_send.

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 output only and clarifies it does not send input, providing clear context. It does not explicitly name alternative tools or state exclusions, but the context is sufficient for most use cases.

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