get_session_detail

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

No annotations provided. Description lists return fields but does not mention side effects, permissions, or rate limits. Since the tool is read-only, a 3 is adequate but lacks depth beyond the return data listing.

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?

Concise, three-section structure: purpose, return details, usage context, parameter docs. No superfluous words. Every sentence adds value.

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?

Output schema exists but not shown. Description lists extensive return fields (page visits, events, etc.). Could mention potential errors or limits, but nearly complete for a detail lookup tool.

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 has 0% description coverage for 'session_id' (just type string). Description adds: 'session_id: The session primary key (UUID) from get_sessions results,' specifying type and source. Fully compensates for schema gap.

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?

Clearly states 'Get full details for a specific session.' Lists specific return data (page visits, event timeline, etc.) and differentiates from sibling tools like get_sessions (list) and get_site_stats (aggregate).

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 states 'Use this to deep-dive into a specific session after finding it via get_sessions.' Provides clear context and precondition. Could add when not to use, but sufficient for a detail-retrieval tool.

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