rybbit_get_user_sessions

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

With no annotations provided, the description carries the full burden. It only states 'Get session data for a specific user' and does not disclose what data is returned, whether it returns a list, pagination, filtering behavior, or any access requirements. This is minimal and leaves much behavior unspecified.

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, tightly-worded sentence with no redundancy. It front-loads the verb and object and earns its place.

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 tool has no output schema and no annotations, so the description should explain what 'session data' means and what is returned. The one-liner is too sparse to fully inform an agent about the return shape or scope, especially given the many sibling session tools.

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?

Both parameters (siteId, userId) have schema descriptions, providing 100% coverage. The description does not add additional semantics beyond the schema, such as formats or relationships. Baseline 3 is appropriate as the schema handles the meaning.

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 states the action ('Get') and resource ('session data') with a specific scope ('for a specific user'), differentiating it from broader session tools like rybbit_get_sessions. The verb and object are unambiguous, though the exact nature of 'session data' is not elaborated.

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?

No guidance is provided on when to use this tool versus alternatives such as rybbit_get_sessions or rybbit_get_session_details. There are no prerequisites, exclusions, or examples to help select this tool.

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