rybbit_get_user_session_count

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description only states the action and does not mention side effects, return format, timezone handling, or whether it is a safe read operation. This is a significant gap.

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?

A single, direct sentence that clearly front-loads the action and resource. No filler or redundant text.

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 is simple, but with no output schema, the description should explain the return value structure. It only says 'number of sessions per day' without specifying the format (e.g., array of dates and counts) or how timeZone affects the daily aggregation. This leaves the agent without enough context for a complete invocation.

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 description coverage is 100% for all three parameters (siteId, userId, timeZone). The description adds no extra meaning beyond the schema; it merely repeats the 'specific user' concept. Baseline of 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?

The description clearly states the verb ('get'), resource ('number of sessions per day'), and scope ('specific user'). It distinguishes from siblings like rybbit_get_user_sessions by focusing on a daily count rather than session details, but it does not explicitly name alternatives.

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?

Usage is implied from the purpose: use when needing a daily session count for a user. However, there is no explicit guidance on when to use this tool versus siblings like rybbit_get_user_sessions, nor any conditions or exclusions.

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