superset_get_dashboard_charts

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states the basic read operation without describing any limitations, prerequisites, potential errors, or response format (though an output schema exists). It does not disclose whether the tool returns full chart objects, pagination behavior, or how 'belong to a dashboard' is defined, leaving significant behavioral ambiguity.

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 short sentence with no filler or redundant information. It is front-loaded and immediately communicates the core action and target. Every word earns its place, making it highly concise and structurally efficient.

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 existence of closely related sibling tools (superset_list_charts, superset_get_dashboard, superset_add_chart_to_dashboard), the description lacks contextual guidance on how this tool fits in. The one-sentence description is insufficient to fully understand the tool's role, especially with no parameter semantics or behavioral nuance. The output schema may cover return values, but the description still needs to provide more operational context to be complete.

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% and the description does not compensate. The only parameter, dashboard_id_or_slug, is mentioned in the name but its format, semantics, and usage are not explained in either the schema or the description. There is no guidance on how to obtain or format the value (e.g., ID vs. slug), making parameter understanding reliant solely on the variable name.

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 tool's function: 'Get all charts that belong to a dashboard.' It uses a specific verb (Get) and resource (charts) with an explicit qualifier (that belong to a dashboard), distinguishing it from sibling tools like superset_list_charts (all charts) or superset_get_dashboard (a single dashboard).

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 when to use the tool (when you need charts for a specific dashboard) but provides no explicit guidance on when not to use it or how it compares to alternatives like superset_list_charts or superset_get_dashboard. There is no mention of exclusions or preferred scenarios, so usage is only implied.

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