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

Annotations already cover readOnly/destructive/openWorld, so the bar is lower, and the description still adds real value: it discloses that integration secrets are stripped from properties, which is a meaningful data-safety detail an agent cannot infer from annotations. It also gives the underlying endpoint.

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?

Very compact: one sentence covering contents, the secrets-stripping caveat, and the endpoint. Front-loaded with the resource description. Slight redundancy with the endpoint line, but nothing wasteful.

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 carries the burden of describing returns and does so (widgets, feeds, position, properties). For a single-parameter read tool with readOnly annotations, it is close to complete; only result shape depth (pagination/count) is unstated.

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 coverage is 100% and there is only one required parameter, so the schema fully documents dashboard_key. The description only implies which dashboard via 'of a dashboard' and adds no format or example syntax beyond the 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?

The description names the specific resource returned (dashboard blocks/widgets) and enumerates example widget types, so the agent knows exactly what this returns. It does not explicitly contrast itself with siblings like get_dashboard or list_dashboards, which is the only gap.

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?

There is no guidance on when to use this versus get_dashboard (which likely also surfaces blocks) or list_dashboards. The HTTP path implies a straightforward read, but no conditions or alternatives are stated.

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