get_session_detail

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

Annotations already declare readOnlyHint and idempotentHint, so the tool's safety profile is known. The description adds value by detailing the return content (metadata, original task, files modified, last assistant message), which goes beyond the annotations and clarifies what 'full details' means.

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 concise, two sentences with the primary action stated first and the return contents summarized in a bullet-like list. No unnecessary words or repetition.

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 tool with one well-documented parameter, an output schema, and clear annotations, the description fully covers what the tool returns and when to use it. There is no missing behavioral context that would impede an agent from invoking it correctly.

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?

The schema provides a complete description for the single parameter (session_id with example), and the description does not add further parameter-specific semantics. Since schema coverage is 100%, the baseline of 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 details of a specific session.' It specifies what is included (metadata, original task, files modified, last assistant message), which distinguishes it from sibling tools like get_session_messages and list_sessions by focusing on a single session's comprehensive detail.

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 when to use this tool (when you need full details on a single session), and the inclusion of specific elements (metadata, original task, files modified, last assistant message) suggests what you might use it for. However, it lacks explicit guidance on when not to use it or how it compares to alternatives like get_session_messages.

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