Dashboards: set home

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

Annotations already flag the destructive mutation. The description adds crucial context: it replaces your previous home, affects only your own landing dashboard, leaves other users unaffected, and recommends confirming with the user. This scope-of-effect detail goes beyond the annotations and is exactly the kind of behavioral context needed.

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?

Front-loads the purpose in the first sentence and follows with scoping, alternatives, and a safety note. The sentence 'Returns JSON' is minor filler, but overall structure is efficient with no major redundancy.

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 is destructive (annotations cover this), takes one fully-described parameter, and has no output schema, the description supplies all additional information an agent needs: exact effect, user-scope, alternatives, and a confirmation warning.

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%, with the sole parameter 'id' fully documented in the schema, including where to find it. The description does not add anything beyond the schema, so the baseline of 3 applies.

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 and resource: making one of your dashboards your landing dashboard. It explicitly distinguishes from siblings by naming dashboards_promote_to_default for changing the default new users start from.

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?

Provides explicit when-to-use guidance, including the alternative tool for a different use case (dashboards_promote_to_default) and a validation step via dashboards_mine. Also advises checking with the user before running due to its destructive nature.

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