Goal Sessions

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint, openWorldHint), so the description only needs to add selection behavior. It states that only sessions completing a specific goal are returned, which is useful, but does not disclose response format, pagination, or time-range behavior.

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, front-loaded with the action and scope, with no redundant phrases. The second sentence adds a genuine use case without bloat.

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 read-only filtered-list tool, the description plus schema covers required params, pagination, filters, and date handling. It lacks an explicit return-shape statement, but the absence of an output schema is mitigated by the straightforward 'sessions' result type.

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%, so every parameter (siteId, goalId, page, limit, dates, filters, timeZone, pastMinutes) already has a description. The tool description adds no parameter-level detail beyond the schema, so it stays at the baseline 3.

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 states a specific verb ('Get'), resource ('sessions'), and a clear scope ('that completed a specific goal'), which differentiates it from generic list_sessions or single-session tools. It does not explicitly name a sibling alternative, but the goal-specific qualifier makes the tool's role unambiguous.

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?

'Useful for analyzing which users and sessions triggered goal conversions' provides a clear analytical context. It does not list exclusions or explicitly point to alternatives, but the stated use case is direct enough for an agent to select this over generic session tools.

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