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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'opens nothing by itself', which prevents the agent from assuming a side effect. It adds the useful detail that the return value is procedural text (screens, buttons, fields), though it says nothing about length or formatting of that output.

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 core guidance is front-loaded and useful, but the trailing sentence about SysAid's Connect API and the absence of an official MCP server (with a check date) is tangential to invoking this tool and adds noise. The final clause about the browser tools is buried at the end of a long sentence.

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 zero-parameter, non-mutating guidance tool with no output schema, the description covers what it returns and what it does not do, which is the essential information. Missing are how the ticket is identified and whether the returned steps are SysAid-version specific.

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 tool takes zero parameters, so the schema needs no elaboration and the baseline of 4 applies. The description could note how the target ticket is identified if it is not passed as a parameter, which is an unresolved gap.

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 and resource (resolve a ticket in the user's own SysAid account) and immediately clarifies the tool's real nature: it returns step-by-step instructions rather than performing the resolution. It does not explicitly distinguish itself from write-capable siblings like sysaid_update_ticket, so the agent must infer the split from the 'opens nothing by itself' wording.

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?

It gives a clear use path: call this to get the screens/buttons/fields, then carry it out with the cotlet_browser_* tools. It does not state when NOT to use it (e.g., if the user's plan allows a direct API action) or why one would pick it over sysaid_update_ticket for the same ticket.

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