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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and openWorldHint. The description adds useful behavioral context beyond annotations: no login is required, output is grouped by area, each entry includes read/write status, required scope, and availability to the current session. It does not need pagination or mutation details for a zero-parameter read-only tool.

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?

It is front-loaded with what the tool returns, immediately followed by explicit call conditions and relay guidance. Despite being information-dense, every sentence serves a distinct purpose: output scope, triggers, presentation style, and authentication requirement.

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?

With no input parameters, no output schema, and read-only annotations, the description supplies everything an agent needs: what it returns, the grouping and metadata per tool, when to call it, how to relay results, and that no login is required.

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 parameter semantics are not a meaningful source of ambiguity and the baseline is high. The description correctly avoids discussing parameters and instead clarifies the structure of the capability listing.

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 gives a specific verb and resource: lists everything a Squish connection or assistant can do, grouped by areas and annotated with tool metadata. It is unmistakably distinct from all operational sibling tools like check_ssl or list_my_domains because it is explicitly a capability inventory.

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 names exact triggering questions: what you can do, what the connection can do, what a read-write key adds, or whether something is possible over MCP. It also gives a behavioral instruction to relay areas in plain words and name tools only on request.

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