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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context by naming the fields returned, which matters because there is no output schema. It does not cover pagination or result-size behavior, 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?

Two tight fragments with the highest-value information (what is returned) front-loaded. 'GET /dashboards' is a mild redundancy for an MCP caller, but it is short and harmless.

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?

For a parameterless read-only list tool with no output schema, the description supplies exactly the missing piece: the shape of the returned records. Safety context comes from annotations. Pagination/rate-limit behavior is the only remaining gap, which is minor here.

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 per the baseline the description needs to add nothing. The listed return fields are not parameter semantics but do add adjacent value without conflicting with the empty 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?

Clear verb + resource: lists the account's dashboards, and it even enumerates the returned fields (key, name, description, visibility). It implicitly distinguishes itself from list_feeds/list_groups through the resource noun, but never names an alternative (e.g. get_dashboard for a single dashboard), so it stops short of full sibling differentiation.

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?

The scoping phrase 'the account's dashboards' implies when this tool applies, but there is no explicit when-to-use guidance and no mention of the sibling get_dashboard for retrieving one dashboard's detail. Usage is inferable from the name and resource rather than stated.

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