Get session detail

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

Describes output (session metadata plus ordered events) but lacks annotation support. No mention of side effects, auth requirements, or rate limits. With no annotations, description provides basic behavioral context but not comprehensive.

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?

Single sentence front-loaded with purpose and scope. No redundant words. Highly efficient.

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?

Given no output schema, description adequately outlines return structure (session metadata + ordered events). Missing details on pagination implications or event types, but sufficient for a single-session fetch.

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 80% (4 of 5 parameters described). Description adds no parameter meaning beyond schema, so baseline 3 applies. No enrichment.

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 detail for a single session by ID' with specific resources (session metadata, ordered list of events). Distinguishes from siblings like rybbit_list_sessions and rybbit_get_overview by specifying the full detail for one session.

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?

Implies use case (retrieving full session detail) but does not explicitly state when to use vs alternatives or provide exclusions. No guidance on when not to use.

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