get_session

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose the primary output ('summary metadata and a frontend link') and implies a read-only retrieval, but it does not mention error behavior, authorization requirements, or what happens when an ID does not exist.

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 with no filler. The core function is front-loaded, and the usage constraint is stated separately and clearly. Every sentence 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?

Given the tool's simplicity, one required parameter, and the presence of an output schema, the description is nearly complete. It explains what the tool returns and when to use it. The only notable omission is behavior for invalid or missing session IDs, which is a minor gap for a direct lookup tool.

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 for the undocumented session_id parameter. It adds that the parameter is a ReclaimLLM session ID and that it should be a specific identifier, but it does not specify format, source, or examples. This is adequate for a single self-explanatory parameter but not rich.

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 action ('Return summary metadata and a frontend link') and the target resource ('a specific ReclaimLLM session ID'). It distinguishes get_session from listing/searching tools by emphasizing lookup by ID, though it does not explicitly contrast with the sibling summarize_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?

The description provides an explicit use condition: 'Use only when the user asks to look at a particular session by ID.' This is clear guidance, but it does not name alternative sibling tools or explain when a different tool would be more appropriate.

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