List Views

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe/read-only nature is covered. The description adds actionable behavioral detail: template variables in filters are resolved to the authenticated user's values, which is not captured in annotations or schema. This is a meaningful addition beyond what structured fields already communicate.

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 two sentences, front-loaded with the endpoint and action. It contains no filler or redundancy, every word 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?

For a list operation with no required parameters, good annotations, and a clear endpoint, the description covers pagination and a non-obvious behavior (template variable resolution). No output schema exists, so the response structure is not explained, but this is a minor gap for a simple list tool. Overall, it is sufficient for an agent to invoke correctly.

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 covers 100% of parameter descriptions, including limit, cursor, and order_by with clear explanations. The description's mention of cursor-based pagination aligns with the cursor parameter but does not add new details beyond the schema. Hence, baseline 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 action ('List all views') and resource ('views'), with a specific endpoint. It distinguishes from sibling tools like gorgias_get_view (single view) and gorgias_list_view_items (items within a view) by indicating this is a list operation for views.

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 implies the tool is for listing views, and mentions cursor-based pagination, but does not explicitly state when to use this versus alternatives (e.g., gorgias_get_view for a single view). The context is clear enough, but no exclusions or alternative recommendations are provided.

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