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

Annotations already declare readOnly, idempotent and non-destructive behavior, so the bar is lowered. The description still adds real context the annotations do not: an initial page of 'up to 100 items' and the reinforcing 'Not for changing data'. It does not explain what 'open' physically does (navigation vs. render), keeping it from a 5.

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?

Three short, front-loaded sentences with no padding, and the routing hint comes first. The middle sentence ('Support websites, conversation activity and help articles') is a slightly loose content list but still earns its place by scoping what can be browsed.

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?

An output schema exists, so return values needn't be described; the description covers when to use it, the browsing scope, and the initial item cap. It is essentially complete for a no-argument view-opening tool, though the relationship to the other show_* tools remains unaddressed.

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?

There are zero parameters, so the baseline is 4. The description correctly adds no parameter detail because none exists; the 100-item default is behavioral, not a parameter.

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 verb (open) and resource (Supovia) and clarifies the interactive-browsing scope, which distinguishes it from the get_/list_/search_ siblings. It does not explicitly contrast itself with the other 'show/open' siblings (show_customer_inbox, show_support_overview), so it falls short of a 5.

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 when-to-use ('when someone wants to open Supovia and browse their workspace interactively') and one exclusion ('Not for changing data'), but it never names an alternative or distinguishes itself from the similar show_* siblings that also surface a view. Usage is implied rather than routed.

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