plot_polar_chart

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

No annotations exist. The description indicates it returns a dict but does not disclose whether the tool is read-only, modifies data, or has side effects. The behavior is unclear.

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 includes redundant phrases like 'Required Argument.' repeated for each parameter. It is front-loaded with a summary but parameter details are unnecessarily verbose and contain errors, making it less concise.

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 lack of output schema and annotations, the description should explain the return format and data expectations for a polar chart. It only says 'dict' and fails to clarify how labels and columns relate to the chart's angles and radii.

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?

Parameter descriptions in the schema are copied from the description text and are misleading: table_name mentions 'donut plot', labels and column mention 'line plot', which contradict the tool's polar chart purpose. Schema coverage is 100% but adds no value and introduces errors.

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 initially states 'polar area plot', but parameter descriptions refer to 'donut plot' and 'line plot', causing confusion. The purpose is vague and inconsistent.

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?

No context is provided on when to use this tool versus sibling tools like plot_line_chart, plot_pie_chart, or plot_radar_chart. The description lacks usage guidance.

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