generate_area_chart

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

Annotations provide readOnlyHint=true, indicating this is a safe read operation. The description adds context about interpreting area size for distance inference in the velocity-time example, which is useful behavioral insight beyond annotations. However, it doesn't mention output format (image, URL, etc.), performance characteristics, or error conditions.

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 reasonably concise but could be more front-loaded. The physics example is helpful but extends the length. The first sentence states the purpose clearly, but the example takes significant space without adding critical information beyond the initial purpose statement.

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 chart generation tool with rich schema documentation (100% coverage) and read-only annotations, the description provides adequate context about when area charts are appropriate. However, with no output schema and many sibling visualization tools, it could better differentiate this specific chart type and clarify what gets returned (image data, URL, etc.).

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?

With 100% schema description coverage, the schema already documents all 9 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. The velocity-time example illustrates data structure but doesn't provide additional parameter guidance beyond schema documentation.

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 generates an area chart to show data trends under continuous independent variables, with a specific physics example. It distinguishes from siblings by focusing on area charts for continuous data trends, but doesn't explicitly contrast with line charts or other trend visualization siblings.

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 usage for continuous independent variables and observing overall data trends, with a velocity-time example. However, it doesn't provide explicit guidance on when to choose this over alternatives like line charts or other trend visualization tools among the many siblings, nor does it mention when not to use it.

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