plot_polar_chart

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

Annotations already declare readOnlyHint and idempotentHint, so safety is clear. The description adds that it returns a dict but does not explain what the dict contains. It mentions 'generate a polar area plot' but lacks detail on output format or side effects beyond annotations.

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 verbose and repeats parameter details already in the schema. It is not front-loaded and contains contradictory terminology (donut, line). Shorter, clearer exposition would be more effective.

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 existence of sibling plot tools and no output schema, the description should clarify the format of labels and column (e.g., comma-separated), and explain the output dict. It fails to provide this context, making the tool less usable.

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% but the parameter descriptions in both schema and description are identical and vague (e.g., 'Specifies the labels to be used'). The description adds no meaningful semantics beyond the schema, and the text incorrectly uses 'donut' and 'line' instead of 'polar', causing confusion.

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 states it generates a polar area plot, using labels and a column. This verb+resource is specific and distinguishes from sibling line, pie, and radar charts. However, the text inconsistently refers to 'donut plot' and 'line plot', which slightly reduces clarity.

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 guidance on when to use this tool versus alternatives like plot_line_chart or plot_radar_chart. No prerequisites or use cases mentioned, leaving the agent without context for selection.

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