superset_dashboard_charts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the return value (chart IDs and names) and scope ('all charts'), but does not mention error handling, permission requirements, or pagination. This is minimal but not contradictory.

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 extremely concise, consisting of three short sentences that state purpose, output, and argument. It is front-loaded and contains no filler or redundant content, every sentence earns 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?

For a simple single-parameter tool with an output schema, the description is reasonably complete. It specifies what the tool does, what it returns, and identifies the parameter. The absence of alternative tool references is a minor gap, but not critical for this level of complexity.

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's 'Args' section merely repeats the parameter name, providing no additional meaning beyond the schema. With schema description coverage at 0%, the description fails to compensate, offering no context about where to find the dashboard_id or any constraints beyond it being an integer.

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 uses the specific verb 'Get' and clearly identifies the resource: 'the list of all charts placed on a dashboard.' This distinguishes it from sibling tools like superset_chart_list (which lists all charts) and superset_dashboard_get (which retrieves dashboard details).

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 implies a use case ('Useful for analyzing dashboard contents') but does not explicitly state when to choose this tool over alternatives or mention exclusions. It could have indicated to use superset_dashboard_get for dashboard-level metadata or superset_chart_list for a global list of charts.

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