websex_engagement_get

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read ("Return metadata") but says nothing about error behavior for unknown IDs, permission requirements, or whether the engagement is scoped to a workspace/session. An output schema exists, so return format is at least covered elsewhere.

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 tight sentence with the resource and the singular-scope qualifier front-loaded. No filler.

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 get-by-id tool with an output schema covering return values, the description is minimally sufficient. The gaps are the missing provenance of the ID and the absence of any error/permission behavior, which matter more here because there are no annotations to fall back on.

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 the single required engagement_id, so the description must compensate. It does add one meaningful semantic: the ID is "server-generated," signaling the agent cannot construct it and must source it from create/list. It does not describe the ID's format or where to find 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 ("Return metadata") and resource ("one ... engagement ID"), and the singular "one" implicitly separates it from the plural websex_engagement_list and from websex_engagement_create. It stops short of explicitly naming those siblings, so it lands at 4 rather than 5.

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 gives no when-to-use guidance, no prerequisites, and no reference to the sibling tools (create/list/plan) that would tell an agent how to obtain an engagement ID. Usage must be inferred from the name alone.

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