session_lease_info

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It reveals only that it 'never returns the token', which is a safety trait, but it does not state whether the operation is read-only, side-effect-free, or any error/response behavior beyond that. For a tool that presumably queries state, more transparency is needed.

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 sentence that front-loads the primary action and safety constraint. There is no wasted wording, and the 'never returns the token' caveat is placed right after the purpose, which is especially relevant for an agent deciding whether to call this tool.

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?

With no output schema, the description should clarify what the tool returns (e.g., whether it returns a boolean, status text, or structured lease info). It also omits behavior for missing sessions or invalid parameters. While the schema offers some guidance on session naming, the description is too thin to fully prepare an agent for invoking the tool.

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 100%, so the parameters 'name', 'lease', and 'session' are already fully documented. The description itself adds no parameter-specific meaning beyond the schema. Since the schema covers all parameters, the baseline 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 clearly states the action ('Report the lease state') and the target resource ('for a session'). It explicitly adds 'never returns the token', which distinguishes it from sibling tools like session_lease and session_release that likely return tokens. This makes the purpose unmistakable.

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 usage for checking lease state but does not explicitly say when to use it vs. alternatives. It does not mention 'use this before acquiring a lease' or 'use this to verify lease status'. However, the sibling context suggests it is a read-only counterpart to lease/release, which is implicit. No exclusions or alternatives are stated, so it meets only the minimum viable.

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