create_arrow_chart

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It mentions the output structure (filepath, title, rows) and color coding but does not disclose potential side effects (e.g., file creation, permissions, or data persistence). This is adequate but leaves questions about behavior beyond the immediate output.

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 with three focused sentences: one defining the chart, one listing ideal uses, and one summarizing the return format. No wasted words; each sentence serves a clear purpose.

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 presence of an output schema (as indicated by context signals) and full schema coverage, the description provides sufficient context for a simple chart creation tool. It mentions return shape and use cases, leaving no obvious gaps for the agent to infer.

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 input schema has 100% coverage, so the description adds limited additional meaning beyond parameter names and types. It provides context for the data (directional changes) and colors, but does not elaborate on parameter formats or constraints beyond what the schema already declares.

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 explicitly states it creates an arrow-style chart for showing directional changes, with clear color coding (green=positive, red=negative). It distinguishes itself from sibling chart tools by specifying the chart type and use cases like rankings change, budget surplus/deficit, and growth/decline.

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 provides ideal use cases (rankings change, budget surplus/deficit, growth/decline), giving context for when to use this tool. However, it does not explicitly contrast with sibling chart tools or state when not to use it, which would enhance decision-making.

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