get_session

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

No annotations are provided, so the description carries the full behavioral burden, yet it never states that this is a read-only operation, what happens when the session_id is unknown, or what 'progress' contains (counts, completion percentage, timestamps). The one genuinely useful disclosure is the lifecycle behavior that a summary appears only once the session finishes.

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?

It is a single front-loaded sentence with no filler, so nothing is wasted. However, this brevity reflects under-specification rather than efficiency, and the parenthetical forces the reader to reconstruct the tool's two modes.

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 tool with no annotations, no output schema and two undocumented parameters, the description leaves essential gaps: return shape is only hinted at, and the user_id/session_id relationship is unexplained. An agent could call it, but not confidently interpret the result or know how to handle an invalid or finished session.

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 explain session_id and user_id, and it explains neither. The defaulted user_id parameter is especially opaque: nothing says whose session is resolved or whether user_id scopes session lookup.

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?

It names the resource (session) and what it returns (progress, and a summary once finished), so the agent knows the general shape of the result. But there is no explicit verb and no differentiation from nearby siblings like get_progress, get_coverage or get_next_question_brief, so the agent must infer whether this is session metadata, live progression, or a retrospective.

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 gives no indication of when to call this versus get_progress or get_next_question_brief, and it states no prerequisites such as whether the session must be active or finished. The parenthetical about the summary hints at a lifecycle distinction but never tells the agent to prefer another tool.

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