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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's real contribution is disclosing the shape of the payload it returns — space, participants, guests, tags, summary, recording state. With no output schema present, that enumeration is genuinely load-bearing, though error behavior (e.g. unknown uuid) is unaddressed.

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?

Two short sentences, front-loaded with the identification and scope, followed by the raw endpoint for API-aware callers. Nothing is padded.

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 single-parameter read tool with annotations covering safety and no output schema, listing the returned facets makes the definition largely complete. Minor gaps remain around error/not-found behavior and whether the response is nested or flat.

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% and the schema itself tells the agent the value is the `uuid` field from lessonspace_list_sessions. The description only repeats 'by uuid,' adding no format or constraint detail beyond the structured field.

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 ('One session by uuid') and enumerates the returned facets (space, participants, guests, tags, summary, recording state), which separates it from list_sessions and, by omission of the media itself, from get_session_recording. It never names a sibling explicitly, so differentiation is inferential rather than stated.

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?

'One session by uuid' implies the single-item fetch case as opposed to list_sessions, but there is no explicit when-to-use or when-not-to-use guidance and no mention of prerequisites (e.g. needing a valid uuid from list_sessions, which only appears in the schema).

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