update_dashboard

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

No annotations are provided, so the description carries the full burden. It discloses two important behaviors: only provided fields are changed (partial update) and a GET-then-PUT pattern is used for safety. This adds meaningful context beyond the name, though it omits return values and error handling.

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 two sentences, front-loaded with the action, and contains no filler. Each sentence adds meaningful information: the first defines purpose, the second explains update semantics and safety mechanism.

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 nested objects and no output schema, the description adequately covers the core update behavior but lacks information about return values, error handling, permissions, or limitations. More detail on these aspects would improve completeness.

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% for both parameters. The description adds value by clarifying that the 'patch' parameter is a partial update, meaning unspecified fields remain unchanged—this is not explicit in the schema and helps the agent understand the merge behavior.

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 begins with 'Update an existing dashboard,' clearly stating the verb and resource. It distinguishes from siblings like create_dashboard and get_dashboard_full by emphasizing the update action and partial-update semantics.

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 purpose is clear, but there is no explicit guidance on when to use this tool versus alternatives such as create_dashboard or add_card_to_dashboard. Usage is implied from the name and action, but no when/when-not context is provided.

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