get-dashboards

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

With no annotations, the description carries the full burden, but it does signal read-only behaviour via 'Retrieve' and discloses scope by saying 'every' dashboard (i.e. no filtering or argument-based narrowing). It says nothing about pagination, ordering, or permissions, which are the traits an agent would otherwise need.

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, front-loaded with the action and result, with no filler. The second sentence is mildly redundant on the word 'dashboards' but earns its place by disambiguating which dashboards are meant.

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 no-argument, no-output-schema read tool, the description covers what is returned (dashboard pages plus their widgets) and where they come from. The only remaining gap is pagination/scope limits, which is minor at this complexity.

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 arguments, so per the baseline the schema fully carries parameter semantics and there is nothing for the description to add. The description correctly avoids inventing parameters.

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?

Names a specific verb (Retrieve) and resource (every dashboard page and its widgets), and the second sentence locates them in the Reports section of the sidebar. It is clear what the tool returns, but it never distinguishes itself from report-oriented siblings like get-custom-reports or net-worth.

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?

Usage is implied by the resource named rather than stated: an agent can infer this is the tool for dashboard layouts. There is no explicit when-to-use guidance, no exclusion of cases where get-custom-reports would be preferred, and no mention of prerequisites or sidebar/UI state.

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