apex_add_gradient_donut

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

No annotations provide protective hints (all false), and the description does not disclose side effects, prerequisites, or whether it modifies the page. Since the verb 'Add' is mutation, but the description doesn't elaborate on what occurs (e.g., new region created), behavioral transparency is lacking.

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 a single sentence that front-loads the core function and includes a useful SQL hint. It is extremely concise with zero wasted words.

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?

While the schema and output schema handle parameter documentation, the description lacks behavioral and contextual detail for a tool with 16 parameters. It doesn't explain how the gradient donut chart integrates with the page or what the expected outcome is beyond adding it.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description adds 'SQL: LABEL, VALUE' which reinforces the sql_query parameter but doesn't provide additional semantics beyond the schema. Thus a 3 is appropriate.

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 'Add a gradient donut chart with center label' which clearly identifies the verb (Add) and resource (gradient donut chart with center label). It also specifies the SQL column expectation (LABEL, VALUE), distinguishing it from generic chart tools like apex_add_jet_chart.

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 gives minimal usage guidance: it implies this tool is for adding donut charts, but doesn't explicitly say when to use it over siblings like apex_add_funnel or apex_add_sparkline. No exclusions or alternative recommendations are provided, so usage context is only inferred.

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