Describe Session

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so no contradiction. The description adds transparently that the full session record includes all event messages and final text output, providing useful behavioral context about what can be expected from the response.

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 efficiently composed in two sentences, front-loaded with the primary purpose ('Get detailed information') followed by a concise elaboration of what is returned. There is no redundancy or filler.

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 simple tool with a single parameter, an output schema present, and annotations covering safety behavior, the description provides all necessary context. It explains what kind of information is retrieved, making it complete for correct selection and invocation.

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 covers 100% of parameters with a clear description for session_id, and the tool description does not need to compensate. It does not add additional semantics beyond the schema's own description, so a baseline score 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 uses a specific verb 'Get' targeting 'agent session' and provides distinguishing detail about returning the full session record including all event messages and final text output. This clearly separates it from sibling tools like 'describe_session_token_usage' which focuses on token usage.

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 use for retrieving detailed session information but does not explicitly state when to use it over alternatives or mention any exclusions. Sibling tools like 'get_sessions' and 'describe_session_token_usage' are not referenced, leaving usage context only implied.

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