diagnose_session

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

With readOnlyHint/openWorldHint already covering the safety profile, the description adds genuine behavior: results are keyed by aspect name, a failed aspect returns {"error": ...} instead of aborting the call, and the tool internally resolves internal_session_id. It stops short of permissions or performance/rate-limit context.

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?

Three short paragraphs, front-loaded with purpose and aspect list, then error semantics, then the ID caveat. Each sentence carries information, though the 'verified live' anecdote is slightly more verbose than needed.

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 an output schema present, return formatting need not be restated, and the description covers the remaining essentials: what aspects exist, what partial failure looks like, and the ID resolution quirk. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3; the description goes beyond it by warning that the underlying help desk endpoints need internal_session_id, not session_id, and that the tool transparently performs that lookup — non-obvious semantics the schema does not capture.

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 and resource ('Retrieve diagnostic information for a user session') and enumerates the exact diagnostic aspects it can return, which cleanly separates it from the sibling read tools get_session and list_sessions.

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?

Establishes clear context ('in a single call', fetching any combination of aspects) so the agent knows this is the aggregated diagnostic path, but names no explicit exclusions or alternatives such as get_session.

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