get_chart_data

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

No annotations are present, so the description carries the full burden. It discloses that 'force bypasses the Superset cache,' which is useful, but it does not explicitly state that the operation is read-only, error behavior, or return format. The core behavior is clear, but some transparency gaps remain.

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 one concise sentence, front-loaded with the primary action and appending the cache-bypass detail. Every word earns its place, with no redundancy or extraneous information.

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's simplicity (two parameters, no output schema), the description is largely sufficient. It covers the main function and one parameter's behavior, but lacks details on return data structure or error conditions. This is a minor gap in an otherwise adequate description for a straightforward read tool.

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 schema has 0% description coverage, so the description must compensate. It explains the 'force' parameter's cache-bypass effect, but 'chart_id' is only self-evident from its name. This partial coverage is helpful but not fully compensating for both 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?

The description clearly states a specific verb and resource: 'Run the stored chart query and return its data.' It distinguishes this from siblings like get_chart (chart metadata) and get_sql_result (arbitrary SQL), as it targets saved chart queries.

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 description provides no explicit when-to-use guidance or mention of alternatives. The context of sibling tools implies usage, but there is no stating of when this should be used over get_sql_result or other fetch tools.

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