Get View

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds little beyond the schema's parameter info, but it doesn't contradict annotations or hide any surprising behavior. It lacks extra context like error handling or return format, but for a simple GET 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 sentence with zero waste, front-loaded with the HTTP method and resource path. It communicates the essential action immediately and efficiently.

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 simple one-parameter GET endpoint with read-only annotations, the description is sufficiently complete. It states the action, resource, and parameter. It doesn't describe the response shape, but no output schema exists and the operation is standard, so this is a minor gap. Overall, the description provides enough context for an agent to select and invoke the tool 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?

The input schema already provides 100% coverage for the single 'id' parameter, including a description. The tool description's phrase 'by its unique ID' slightly reinforces the parameter's purpose, but it doesn't add meaningful new semantics beyond the schema.

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 ('Retrieve') with a clear resource ('a single view') and scope ('by its unique ID'). It clearly distinguishes from sibling tools like gorgias_list_views (list all) and gorgias_update_view (modify).

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 context is clear: use this when you have the specific view ID and need that single view. It doesn't explicitly mention alternatives, but the distinction from similar view tools is fairly obvious from the restful pattern and sibling names.

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