get_session_state

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

Description lists returned fields and state classification, but does not disclose behaviors beyond the return value (e.g., whether it requires an active session, error conditions, or idempotency). No annotations exist to supplement.

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?

Two sentences, front-loaded with purpose, followed by a practical usage hint. No extraneous information. 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 the simple single-parameter schema, the description adequately covers the tool's purpose and output fields, and hints at integration with read_output. However, lacks explicit handling of invalid input or session lifecycle.

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?

Input schema has one parameter (session_id) with 0% description coverage. Description does not elaborate on session_id format, validation, or source, leaving the agent to infer its meaning from context. This is a gap for a required parameter.

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?

Description clearly states 'Get detailed state of a session' and lists specific fields (type, target, is_alive, cursor, classified state) with enumerated state options. This distinguishes it from sibling tools like read_output or send_input.

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?

Provides explicit usage hint: 'Use cursor with read_output(since_cursor=...) for incremental reads.' This tells the agent how to combine this tool with read_output. However, it does not mention when to avoid using it or alternative approaches.

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