superset_chart_get_data

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

With no annotations, the description carries full burden. It discloses the key prerequisite (query_context) and the fallback action, which is critical behavioral context. However, it does not mention error handling, response format details, or whether any side effects occur, leaving some gaps.

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 succinct, front-loaded with the core purpose, followed by the critical IMPORTANT note, and concluding with the parameter list. Every sentence adds value, with no redundancy.

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?

For a tool with an output schema and a moderate complexity, the description covers the main trap (missing query_context) and directs the user to the correct alternative. It does not elaborate on expected output structure, but the output schema covers that. Overall, it is sufficiently complete for usage.

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 0%, so description must compensate. It provides 'chart_id: Chart ID', which is minimal but aligns with the schema. It adds no extra meaning beyond the property name and type, but the parameter is self-explanatory. The description does not explain how to obtain the chart ID or any constraints beyond the integer type.

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 'Get data from a specific saved chart by its ID', with a specific verb and resource. It distinguishes itself from sibling tools like superset_chart_get (which likely fetches metadata) and superset_chart_data (which requires manual query construction).

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?

Explicitly states when to use: 'works only if the chart was saved with query_context' and provides the alternative: 'use superset_chart_data with a manually constructed query'. This is clear when-to-use and when-not-to-use guidance with a named alternative.

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