websex_http_session_get

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

No annotations are provided, so the description carries the full burden, and 'Inspect' only weakly signals a read-only operation. It does add one behavioral detail beyond the schema by disclosing that a history count is returned, but says nothing about permissions, missing-session behavior, or whether the operation has side effects.

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 no filler, and the key qualifiers ('one', 'engagement-scoped') are front-loaded. It is appropriately sized for a simple getter, though the terseness borders on under-specification rather than pure economy.

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?

An output schema exists, so return values need not be explained, and this is a low-risk read operation. Still, with zero schema description coverage and no annotations, the definition leaves the agent guessing about parameter formats and error conditions for a two-parameter lookup.

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% for both required parameters, so the description must compensate and largely does not. 'Engagement-scoped' hints that engagement_id narrows the lookup, but session_id's format and origin are never explained, leaving half the parameter surface undocumented.

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 ('Inspect') and resource ('one engagement-scoped HTTP workbench session') with a singular scope, which implicitly separates it from the plural websex_http_session_list. It does not name any sibling explicitly, but the resource and cardinality are unambiguous.

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 phrase 'one ... session' implies retrieval of a single session by ID rather than a listing, which is enough to infer the split from websex_http_session_list. However, it never states when to prefer this over the list, nor any prerequisites for obtaining a valid session_id.

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