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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds real value by naming the payload contents (workspace, plan status, permissions, mailboxes), which matters because no output schema exists. It stops short of saying whether the response is cached, fails on expired tokens, or requires elevated auth.

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?

A single front-loaded sentence with no filler; the scope qualifier ("this connection's") comes before the enumerated contents. It is appropriately sized for a no-argument 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?

With no parameters, no output schema and safety fully covered by annotations, the one thing the description must carry is what the caller gets back — and it does. Missing only guidance on how this differs from the account/label listing siblings in the same server.

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?

Zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly does not waste words on 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?

Specific verb ("Show") plus an enumerated resource set for the current connection: workspace, plan status, permissions, mailboxes. An agent can tell it is an introspection/status tool rather than a mailbox lister like list_accounts or list_folders, though the description never explicitly names that distinction.

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?

No statement of when to call this versus siblings such as list_accounts or list_send_as, and no prerequisites or exclusions. The only hint of usage is that it reports workspace/plan/permissions, which implies onboarding or capability checks, but the agent must infer that.

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