Read Session Output

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

Disclosures read-only, non-destructive, idempotent behavior, which is consistent with annotations. Adds detail about clearing output and return value. No contradictions.

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?

Description is concise and front-loaded with purpose. Uses structured arg list that is easy to parse. Every sentence adds value.

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 simple tool with only 2 params and no output schema, description sufficiently covers return value and behavior. Lacks mention of error conditions or session state handling, but still complete enough for most agents.

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 baseline is 3. Description adds meaning for session_id (reference to fc_start_session) and clear (optional, clears output), which is consistent with schema. Does not add beyond schema but matches it.

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?

Clearly states it reads output of a running session, specifying return value as output since start/last clear. Distinguishes from siblings like fc_read_file which reads file content, and fc_start_session which creates the session.

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?

Describes when to use (after starting a session) and implies dependency on fc_start_session for session_id. Lacks explicit when-not or alternatives, but sibling list shows clear distinction.

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