get_session_info

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

With no annotations, the description carries the full disclosure burden. It communicates the read-only nature via 'snapshot', lists the exact data included, and specifies the return structure (dict with keys status and data). It does not elaborate on error conditions, but for a simple informational tool this is adequate.

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 highly concise and well-structured: a one-sentence purpose, a clear list of included data, a return format line, and a minimal example. Every sentence adds value with no 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?

For a zero-parameter snapshot tool with an output schema, the description is complete. It covers the tool's purpose, the exact data contents, the return format, and a usage example, making it self-sufficient for an agent to select and invoke 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 tool has zero parameters with 100% schema coverage, so the baseline is 4. The description reinforces this by including a no-argument example call (get_session_info()), leaving no ambiguity about parameter usage.

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 opens with a specific verb and resource: 'Return a snapshot of the current session state.' It then lists the exact fields included, clearly distinguishing it from sibling tools like get_session_history or get_working_directory that target narrower or different aspects of the 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 implies use when a session snapshot is needed, but it does not explicitly state when to prefer this over alternatives such as get_session_history or get_working_directory, nor does it mention exclusions. Guidance is limited to the implied context of 'current session state'.

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