Charts: list

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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior: the newest-first sort order, the returned fields, and JSON output format.

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?

Front-loaded with purpose, then ordering, return shape, filter usage, and domain context. Well ordered; the trailing 'Returns JSON' is minor filler but not harmful.

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 single-parameter read-only list tool with no output schema, the description covers ordering, fields, filtering, and the chart/dashboard relationship. Nothing essential for correct invocation is missing.

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 coverage is 100%, so the single `entity` parameter is already documented as 'Only charts that plot this entity'. The description's 'pass entity to see only one entity's charts' largely restates the schema, so baseline 3 applies.

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?

States a specific verb ('List charts') plus the ordering ('newest first') and enumerates the exact fields returned (id, name, type, data source, entity/metric, last changed). This clearly distinguishes it from siblings like charts_get, charts_create, and charts_delete.

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?

Explains that passing `entity` narrows results to one entity, and clarifies the chart/dashboard relationship ('appears on a dashboard only once added with dashboards_add_chart'). It stops short of explicitly contrasting this tool with charts_get, but the intended use is clear.

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