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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral detail that the payload tracks live state (status, next run time, latest results), but says nothing about behavior for an unknown/stopped session id.

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 short sentence with zero filler, and the resource plus return contents are front-loaded. It reads as a fragment rather than a statement, but nothing needs trimming.

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 read-only getter with a fully documented single parameter and no output schema, this is marginally adequate: it tells the agent what information comes back. It falls short on error behavior and on how the returned statuses relate to sibling lifecycle tools.

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% for the single parameter, and the schema itself explains that session_id comes from start_live_session. The description adds no further meaning, which is the baseline expectation when the schema does the work.

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 names the resource ("One live analysis session") and enumerates what it returns, from which retrieval can be inferred, but it never states a verb. It does not differentiate this from close siblings like list_live_sessions, get_live_analysis, or get_quick_read.

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?

There is no statement of when to use this instead of list_live_sessions (to enumerate) or get_live_analysis (for completed analyses). The only routing hint is the singular phrasing "One ... session", which is implied rather than stated.

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