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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description adds genuinely new context: it 'opens nothing by itself' and returns instructions rather than data, which is exactly the behavioral fact an agent needs to avoid misusing it. The additional note about SysAid having a REST API but no official MCP server explains why the guidance-only design exists.

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 key disambiguation ('opens nothing by itself; then do it with the cotlet_browser_* tools') is well placed, but filler such as 'from ChatGPT, Claude or any AI agent' and the dated aside about the Connect API add length without changing how an agent calls the tool.

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 guidance tool with no output schema, the description supplies what matters: that the return value is step-by-step instructions covering screens, buttons and fields, and which tools to use next. Nothing essential to correct invocation is missing.

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 and the schema is fully closed, so there are no parameter semantics to explain; the description correctly does not invent or reference any inputs.

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 names a specific resource (SysAid tickets) and, crucially, clarifies that the tool does not perform the search itself but returns step-by-step instructions for doing it. This corrects a potentially misleading name ('search_tickets' reads as a data-returning tool), though the opening clause 'Search tickets in the user's own SysAid account' still implies execution before the correction arrives.

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 states the workflow clearly: call this first for guidance, then execute with the cotlet_browser_* tools in the user's SysAid Cloud Browser. It does not name when to prefer a sibling (e.g. cotlet_app_guide) or state exclusions, so it stops short of full routing guidance.

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