set_chart_axis

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

No annotations present, so description carries burden. It discloses return structure and clearing behavior via empty strings, but does not mention permissions, destructiveness, or whether changes are reversible. Adequate but not comprehensive.

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?

Two concise sentences, front-loaded with purpose, no filler. Every sentence adds value: first lists configuration options, second gives critical usage details.

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 11 parameters, 3 required, and no output schema, the description covers purpose, key parameters, and return format. Lacks explanation for path/chart_name and effect on existing settings, but mostly complete for effective use.

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 low (18%), but description adds meaning for axis (Category/Value), axis_name (default Primary, secondary by name), format (in <Style>/<Format>), and clearing via empty strings. Some parameters (path, chart_name) remain implicit, but overall compensates well.

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 verb 'configure' and the resource 'chart axis', explicitly lists configurable elements (title, format, min/max, etc.), and distinguishes between Category/Value axes and the axis_name default, differentiating it from sibling tools like set_chart_title.

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?

Provides guidance on axis_name default vs. secondary axes, and clarifies that passing empty string clears elements. Lacks explicit when-not-to-use or comparisons to alternatives, but context is clear.

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