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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered elsewhere. The description adds real value on top of that: role-based access tiers, that the private service credential stays server-side, and that mailbox passwords and message content are never returned.

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?

Five short, front-loaded sentences that lead with the action and then layer on access and disclosure constraints. No filler, though the access-tier sentence is slightly more detail than strictly needed to select 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?

With no output schema, the description partially compensates by stating what is never returned (mailbox passwords, message content) and who can call it. It stops short of describing what the workspace read actually yields, which is the one gap for a tool with no output schema.

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?

Single parameter with 100% schema description coverage, so the schema fully documents organization_id. The description adds nothing about the parameter's meaning or accepted format, which matches the baseline for a fully covered schema.

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?

States a specific verb and resource ('Read the email workspace'), which is more than a restatement of the title. However, it never distinguishes itself from the closely named sibling commsharbor_email_workspace_snapshot, so an agent cannot tell from the description alone which read tool it wants.

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 lays out a useful access model (no guest access, members read, owners/admins/keys manage), which implies who may call it. But there is no explicit when-to-use guidance and no routing to alternatives such as the snapshot, mailbox_get, or domain_get siblings.

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