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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds billing behavior ('without another session charge'), which is genuine value beyond the annotation, but it says nothing about auth requirements, return format, or whether the retrieval is idempotent.

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?

A single sentence with the retrieval action and the key billing caveat front-loaded. No filler, no repetition of the name.

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 one-param read tool with annotations covering safety and no output schema, the description loosely names the return ('session pack and receipt'). However, it omits any explanation of the required session_id and any sibling differentiation, leaving real gaps for an agent.

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?

Schema description coverage is 0%, so the description carries the burden of explaining session_id but does not mention it at all. The single parameter is fairly self-evident by name, but the description provides no format, sourcing, or scoping meaning for it.

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?

States a specific verb (Retrieve) and resource (session pack and receipt) scoped to 'this account'. The phrase 'without another session charge' further distinguishes it, though 'session pack' is domain jargon and the description never contrasts it with siblings like eclypse_continuity or eclypse_complete_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?

There is no explicit guidance on when to call this versus alternatives such as eclypse_continuity, eclypse_complete_session, or eclypse_start_session. The 'without another session charge' hint vaguely implies a re-fetch scenario but does not state the condition that selects this tool.

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