dashboards_add_card_to_view

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

No annotations provided, so description should disclose behavioral traits like destuctiveness, idempotency, or auto-save. It does not. Only an example card_config is given, which provides no 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?

Two sentences with no waste. First sentence states the action clearly; second sentence provides a useful example. Could be slightly improved by front-loading the required parameters, but overall concise.

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 sibling tools and no output schema details, description lacks context on whether this tool persists changes or requires subsequent save. The example helps but behavioral gaps remain. Not fully complete given the tool's role in a multi-step workflow.

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 0%, so description must explain parameters. It provides an example for card_config but does not explain url_path or view_index format/meaning. The example adds value but is insufficient for all three parameters.

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?

Description clearly states 'Add a card to a specific view in a dashboard.' Verb 'add' and resource 'card' with target are unambiguous. Distinguishes from sibling tool 'dashboards_add_view_to_dashboard' which adds a view, not a card.

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 explicit guidance on when to use this tool vs alternatives. While the purpose is clear, there is no mention of prerequisites (e.g., requiring an existing dashboard and view) or relationship to save_dashboard_config. Implied usage from name but not explicit.

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