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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by listing which fields come back, but says nothing about result size, ordering, or how many dashboards are returned. The idempotentHint=false annotation is unusual for a pure list read, and the description does nothing to clarify it.

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 short sentences, no filler. The enumeration of returned fields comes first and the sibling routing note second, which is the right front-loading for a list 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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them. Combined with annotations covering the safety profile and a fully documented single parameter, nothing an agent needs to call this correctly is missing.

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?

Schema description coverage is 100%, and the single property project_id is documented with both meaning and provenance ('from list_projects'), so the schema carries the load. The description never mentions project_id, nor that it is optional and what scope applies when it is absent. Baseline 3 applies when the schema does the heavy lifting.

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 (the project's dashboards) and enumerates the returned attributes: name, description, tile count, sharing status, last-changed time. It also names the sibling get_dashboard as the single-dashboard alternative, so an agent can distinguish the two without opening either 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?

It gives explicit routing guidance: use this to enumerate dashboards, use get_dashboard for one dashboard's tiles. There is no exclusion or prerequisite note (e.g. what happens if project_id is omitted, or whether results are paginated), so it falls short of a full when/when-not statement.

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