generate_plot_securely

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

No annotations are provided, so the description carries the burden. It discloses the sandboxed, secure execution context and warns about timeouts with large arrays. It does not explicitly state read-only behavior, but for a plotting tool this is implied and not a major gap.

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 two sentences long, front-loaded with the core purpose, followed by usage guidance and a key limitation. Every sentence carries meaningful information with no redundancy.

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 plotting tool with a rich output schema and clear sibling separation, the description covers what it does, when to use it, and the primary performance constraint. The sandbox context adds important environmental awareness. No critical information 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 baseline is 3. The description adds value by mentioning the 10,000-point array limit, which constrains x and y length beyond the schema, and by noting line/scatter options that map to chart_type. It does not explain each parameter individually, but the schema already covers their meanings.

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 line or scatter charts from x and y data in an isolated Azure sandbox. This specific verb+resource combination distinguishes it from sibling tools that handle code execution, CSV sanitization, or GA optimization.

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 explicitly says 'Use this tool to visually represent numerical trends' and provides a concrete constraint ('Keep data arrays under 10,000 points'). It does not mention alternatives or when not to use the tool, so it misses the top tier.

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