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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely non-redundant context: the org-versus-personal visibility boundary and the fact that personal dashboards have no id an account-level MCP key can address, which explains why they are absent rather than silently filtered.

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 sentences, each earning its place: scope, exclusion-with-reason, and downstream routing. The most decision-relevant fact (org-shared) is front-loaded in the first clause.

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, no parameters and rich annotations, the description carries the remaining burden well — it hints at the returned 'id' field and explains the omission of personal dashboards. It stops short of noting result ordering or pagination, a minor gap for an unfiltered list endpoint.

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, so the schema imposes no semantic burden and the baseline is 4. The description correctly spends no space on parameter prose.

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 (List) and resource (org-shared dashboards) with an explicit scope qualifier — 'visible to every account member'. It immediately distinguishes itself from the personal-dashboard surface, so an agent can tell it apart from get_dashboard and the widget catalog sibling without opening a schema.

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?

Gives a clear exclusion ('Does not include any member's PERSONAL dashboard') and routes the agent forward by naming get_dashboard, set_dashboard_widgets and delete_dashboard as consumers of the returned id. It does not, however, say when to prefer this over sibling listers like list_dashboard_widget_catalog, so it falls short of the explicit when/when-not bar.

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