Session Detail

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 fully covered. The description adds the prerequisite workflow (list first) but doesn't mention output shape or pagination, though an output schema exists and covers returns.

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 sentences: the first lists contents, the second gives the ordering prerequisite. Front-loaded and no wasted words.

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 tool with full annotation coverage, complete schema, and an output schema, the description plus structured fields suffice. The only minor gap is not mentioning rate limits or latency, but that's not expected here.

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 both parameters (siteId and sessionId) with clear descriptions. The description adds no parameter-level meaning beyond what the schema already documents, so baseline 3 is appropriate.

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 (Get) and resource (session information) with enumerated contents including page views, events, user traits, device, location, and timeline. Clearly distinguishable from siblings like rybbit_list_sessions or rybbit_get_session_locations, though the enumeration is somewhat listy.

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 directs the agent to use rybbit_list_sessions first to find session IDs, which is a concrete workflow prerequisite. No explicit exclusions or when-not-to-use guidance, but the prerequisite is actionable.

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