dashboards_add_view_to_dashboard

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

With no annotations, the description must disclose behavioral traits. It only states 'Add a new view' implying a mutation, but lacks details on side effects (e.g., whether it overwrites existing views, requires authentication, or has any limitations). The example provides structure but not behavioral context.

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 concise with two sentences. The first states the purpose, the second provides an example. It is front-loaded and to the point, though it could benefit from a brief explanation of url_path.

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 a mutation (add view) with two parameters, the description is too brief. It lacks information about return values, error cases, or how the view fits into the dashboard. The output schema exists but is not leveraged in the description, leaving the agent underinformed.

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?

Parameter schema coverage is 0%, so the description must compensate. It gives an example for 'view_config' but does not describe 'url_path' at all. The example helps understand the view_config format but leaves url_path's purpose and format entirely unspecified.

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 uses the precise verb 'Add' combined with the resource 'view to a dashboard,' clearly distinguishing it from sibling tools like 'dashboards_add_card_to_view' which adds a card to a view. The action and target are unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'dashboards_save_dashboard_config' or 'dashboards_add_card_to_view'). There is no mention of prerequisites, context, or scenarios where this tool is inappropriate.

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