get_session_details

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It mentions the content of the response (events, props, device/geo metadata) but does not address read-only semantics, error conditions, or any need for authentication. Since this is a simple lookup, the description provides reasonable but not comprehensive context.

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?

The description is a single, front-loaded sentence that explains the core purpose and key inclusions. No filler words; every element contributes to the tool's definition.

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?

The description is adequate for a straightforward lookup, listing the key return categories. However, it does not mention the required appId or buildMode parameters, which are available in the schema. Given the absence of an output schema, the description's list of data types is helpful but could be expanded slightly to note the need for both appId and sessionId.

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?

The schema covers all three parameters with descriptions, so the description adds little beyond what's already specified. The mention of 'session id' aligns with the schema's sessionId field, but no additional meaning is given to appId or buildMode. The schema already documents the enum and default for buildMode.

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 clearly identifies the tool's function: it returns session timeline details including events, props, and metadata for a given session ID. It distinguishes this tool from siblings like get_top_events or get_metrics, which focus on aggregated data. However, it lacks an explicit verb, relying on the tool name to convey the action.

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 implies usage when a session ID is available and timeline data is needed, but it provides no explicit guidance on when to choose this over alternatives or any exclusions. It doesn't mention prerequisites like requiring a valid appId or session ID, which are covered in the schema. No references to sibling tools are made.

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