Create View

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

Annotations already declare readOnlyHint=false, so the mutation flag is covered. The description adds the HTTP method 'POST' and a summary of the resource configuration. It does not disclose potential side effects, permissions needed, or return behavior, but with annotations present this is acceptable.

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, front-loaded sentence: 'POST /api/views — Create a new view with filters, sorting, and visibility settings.' Every word contributes; no filler or repetition.

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 12 optional parameters and nested objects, but no output schema. The description is terse and does not explain what the response will be or typical usage combinations. However, the schema is very detailed, partially compensating for the lack of contextual guidance.

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%, with each parameter explained in detail (e.g., visibility enum, filter expression example). The description minimally summarizes these as 'filters, sorting, and visibility settings', adding no new meaning beyond the schema, so baseline 3 applies.

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 and resource: 'Create a new view'. It also lists key features—filters, sorting, visibility settings—which distinguish it from siblings like gorgias_update_view or gorgias_list_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 gives no guidance on when to use this tool versus alternatives (e.g., updating an existing view), no prerequisites, and no context about views in the Gorgias system. The agent must infer usage solely from the tool name and generic 'create' semantics.

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