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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no hint about response shape, scoping, or pagination. It does not contradict the annotations, so no penalty beyond the low value-add.

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 short, but the first sentence is duplicated verbatim and the whole text is boilerplate rather than front-loaded substance. Brevity here reflects under-specification, not conciseness.

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, 0% parameter description coverage, and a nested free-form query object, the description carries the full burden and delivers none of it. An agent has no way to know what dashboards are returned or what the query object accepts without a separate describe_operation call.

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 0% and the schema exposes a generic free-form 'query' object with untyped additionalProperties plus an empty 'params'. The description provides no information about accepted query keys, filters, or formats, leaving the two-parameter surface entirely opaque.

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 is a verbatim restatement of the title ('user-dashboards: GET /api/user-dashboards'), repeated twice. It conveys only the HTTP method and path, nothing about what a user dashboard is or what the call returns. An agent cannot distinguish this from the sibling get_user_dashboards_dynamic_widgets_90e08cce71a18a1630976150 based on this text.

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 only actionable guidance is the pointer to describe_operation for native request schemas, which tells the agent where to look for parameters. There is no statement of when to use this tool versus the sibling dashboards/widgets tools, nor any prerequisites.

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