rybbit_get_goal_sessions

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

With no annotations, the description carries the full burden but only restates that it retrieves completed-goal sessions. It does not mention pagination, ordering, time ranges, or potential side effects, adding marginal value beyond the tool name.

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 concise sentence with no fluff, but it is under-specified for a tool with multiple parameters. It is not as minimal as 'Process', but it lacks necessary elaboration for a non-trivial operation.

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 lacks context about how sessions relate to goals, how to obtain siteId/goalId, or what the response contains. With no output schema and no annotations, this is insufficient for an agent to confidently invoke the tool in all scenarios.

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 parameters with descriptions (100% coverage), so the baseline is 3. The description does not add parameter details, but the schema is sufficient for parameter understanding.

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 uses a specific verb ('Get') with a clear object ('sessions') and a qualifying condition ('that completed a specific goal'), distinguishing it from generic session tools like rybbit_get_sessions and funnel-specific tools like rybbit_get_funnel_step_sessions.

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 provides no guidance on when to use this tool over siblings such as rybbit_get_funnel_step_sessions or rybbit_get_sessions. It only states the basic action, leaving the agent to infer usage context.

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