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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It does so by calling the operation 'Read' and describing the state it returns, making clear this is a non-mutating retrieval. It does not cover error behavior or permissions, but for a simple read 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?

Two tightly packed sentences: the first states what the tool retrieves, the second states when to use it. Every clause contributes information, and the core action is front-loaded.

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?

This is a low-complexity single-parameter read with no output schema, and the description compensates by enumerating the returned state elements (intent, open question, bids, holds). A note on invalid or expired session handling would make it fully complete, but nothing essential is missing for correct 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 already covers the only parameter fully: the session string is documented as 'The session id from an earlier answer' with a pattern and required flag. The description's reference to 'you already have a session id' adds context but not significant new meaning beyond the schema.

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 starts with a specific verb and resource: 'Read the state of a session.' It then enumerates exactly what state is included (intent, open question, bids, holds with status and link), which clearly distinguishes this read-only state tool from mutation siblings like cancel_booking and confirm_booking.

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?

It gives a clear explicit usage directive: 'Use it to pick up a conversation you already have a session id for.' It does not compare against alternatives or provide exclusions, so it falls just short of a 5, but the intended context is unmistakable.

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