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

With no annotations, the description carries the full burden and does disclose meaningful traits: requires a valid Key, anonymous access is disabled, only records for the caller's own role/position are readable, and slug provides explicit authorization. It does not cover pagination or error behavior, but the auth and privacy disclosures are substantive.

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 dense paragraph that front-loads what the tool returns before moving to parameters, prerequisites, and constraints. Every clause adds information, though the run-on structure with multiple colons makes it slightly harder to scan.

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 read tool with no output schema and 0% parameter coverage, the description supplies purpose, return contents, parameter roles, prerequisites, auth, and privacy boundaries. Only the return format/pagination is unaddressed, which is a minor gap given the enumerated content types.

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%, so the description must compensate, and it does: both params are declared required, slug is explained as the explicit-auth credential, and session_id is explained as an identifier sourced from list_sessions/open_canvas. This adds real meaning beyond the bare string types in the schema.

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+resource (retrieve a single session's complete chronological log) and enumerates the content types returned (user messages, AI replies with tokens, tracking events, action calls, screen pushes). This clearly distinguishes it from list_sessions, which is named as the source of session_id rather than as an alternative.

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?

Explicitly tells the agent to obtain a valid session_id from list_sessions or open_canvas before calling, and states the auth/privacy preconditions. It gives strong context but stops short of a formal when-not/alternative clause (e.g., 'for multiple sessions use list_sessions').

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