redash_viz

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

No annotations provided. Description only says 'Create visualizations' without detailing side effects, permissions, idempotency, or limitations. Does not reveal that some parameters (datetime, stacked, suffix) are type-specific.

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?

Extremely concise single sentence. However, it front-loads the main purpose and lists types efficiently. Could be slightly improved by grouping type-specific parameters.

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 8 parameters and no output schema, the description is too brief. Doesn't explain that datetime/stacked/suffix are only relevant for certain types, nor what the tool returns (e.g., visualization ID). Missing key context for proper invocation.

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 description coverage is ~63% (5 of 8 params described). The description merely repeats the type enum already in schema. Does not clarify query_id (e.g., must exist) or name (e.g., unique?). No additional value beyond schema.

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 'Create visualizations' and lists supported types (pie, line, bar, counter). Sibling tools (alerts, dashboards, etc.) are distinct, making the tool's purpose 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 on when to use this tool vs alternatives. Doesn't mention prerequisites (e.g., existing query_id) or situations where other tools (like redash_query) might be more appropriate.

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