Get dashboard widget

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

The annotations already communicate readOnlyHint and openWorldHint, so the bar for added behavioral disclosure is lower. The description adds meaningful context by noting the result is metadata-only and that compact mode strips screenshot blobs, which is behavior beyond what the annotations alone provide.

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?

The description is extremely short and front-loaded, with no filler words. It is slightly elliptical as a sentence fragment, but it earns its place by giving the most important qualification ('metadata only') before the compact-mode detail.

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?

Given the tool has 8 filterable parameters and a rich output schema, the parameter-level details are already covered. However, the description lacks broader context about what dashboard widgets represent and when this tool should be selected over the many sibling tools, leaving an agent to infer usage.

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 high (88%), so the baseline is 3. The description adds value by explaining the otherwise-undocumented 'compact' parameter's effect: screenshot blobs are stripped when compact. It does not need to repeat the parameter docs already present in 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 resource ('Dashboard widgets') and adds a useful qualifier ('metadata only'), making it clear this returns dashboard widget data rather than full report content. It is not a bare restatement of the title, but it does not explicitly distinguish itself from sibling analytics/monitoring tools.

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 description gives no guidance on when to use get_dashboard versus any of the many sibling tools such as get_analytics, get_activity_summary, or search_monitoring. It lacks both explicit alternatives and implied selection criteria beyond the tool's own name.

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