get_session

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds valuable context by revealing that the tool reads the markdown file directly, implying it may bypass indexes or caches, and that the content is full (not truncated). This goes beyond what annotations provide, earning a 4.

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, front-loaded sentence that directly states the action and purpose. There is no redundant information or filler, making it highly concise and efficient.

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 retrieval tool with one parameter, clear annotations, and an output schema present, the description is complete enough. It conveys the key behavioral detail (direct file read) and the output schema covers return values. No further elaboration is necessary.

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% because the only parameter, session_id, has a clear description with an example. The tool description does not add further parameter-level meaning, but the schema already carries the semantic load, so the baseline 3 applies.

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: 'Get full content of a session by reading the markdown file directly.' It specifies a concrete action (get), a resource (session content), and the method (direct markdown file read), which distinguishes it from sibling tools like search_thoughts or open_nodes.

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 by clearly defining what the tool does, but it does not explicitly state when to use it versus alternatives or provide exclusions. It lacks guidance such as 'Use this when you need the raw session content rather than search results.'

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