get_session_context

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

With no annotations provided, the description must disclose behavioral traits. It merely says 'Retrieve' without stating safety (read-only), required permissions, potential errors, or the nature of the returned context. It lacks any depth beyond the basic action.

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 with no filler words. It wastes no tokens and is appropriately sized for the tool's simplicity.

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?

Although the tool has an output schema, the description fails to provide context on what 'full context' includes, any preconditions (e.g., session must exist), or how to retrieve session_id. For a simple one-parameter read tool, this minimal description is inadequate for reliable agent use.

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 has 0% description coverage, so the description should compensate for the sole parameter 'session_id'. However, the description adds no information about the parameter's format, how to obtain it, or its role in the retrieval. The agent is left with only the parameter name.

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 'Retrieve the full context of a session' uses a specific verb and resource, clearly indicating the tool's function. It is implicitly distinguished from sibling tools like 'start_session', but it doesn't explicitly differentiate itself or elaborate on what 'full context' includes, preventing a perfect score.

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?

There is no guidance on when to use this tool, prerequisites, or alternatives. The description does not mention how it relates to session creation or other retrieval tools, leaving the agent without contextual information for selection.

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