execute_dashboard_card_query

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

With no annotations, the description must disclose behavioral traits. It only says 'execute a query', giving no indication of side effects, authorization requirements, or whether the operation is read-only. This is insufficient for agents to reason about safety.

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 a single sentence that is too brief to be useful. It lacks necessary detail while being concise, but conciseness without substance is not valuable. The sentence does not earn its place.

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 complexity (nested input object, many sibling tools, no output schema, no annotations), the description is grossly incomplete. It fails to explain how to structure the input, what the output contains, or when to use this vs. similar execute tools.

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?

The description does not mention any parameters. Despite a schema with multiple fields (id, dashcard_id, card_id, parameters), there is no explanation of their meaning or interplay. Schema coverage is 0%, and the description adds no value.

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 clearly states the action ('execute') and resource ('dashcard query') and mentions 'dashboard filter parameters'. However, it does not differentiate from sibling tools like 'run_dashcard_query' or 'execute_dashcard_action', which perform similar functions.

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 guidelines are provided about when to use this tool versus alternatives. There is no discussion of prerequisites, recommended inputs, or scenarios where this tool is preferred.

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