apex_add_gauge

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

The annotations are all false, leaving the description to explain side effects. The description only states a SQL requirement and the tool's purpose; it does not disclose that this creates a region on a page, whether it is idempotent, or what happens on conflict. This is minimal beyond the 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 a single, concise sentence with no superfluous content. It front-loads the purpose and includes a critical constraint.

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?

The description is brief and relies heavily on the schema, which is rich. However, the statement 'SQL must return a VALUE column' is misleading because the actual column name is configurable via the value_column parameter. It also omits any mention of side effects, though the output schema covers return values. Overall, it is insufficiently complete for a 10-parameter tool.

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% with detailed descriptions for all 10 parameters. The description's mention of 'min/max/thresholds' and 'VALUE column' adds no new information beyond the schema, so it meets the baseline.

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's function: 'Add a gauge/dial chart with min/max/thresholds.' It uses a specific verb and resource, and the mention of min/max/thresholds distinguishes it from sibling chart tools like apex_add_jet_chart or apex_add_sparkline.

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?

There is no explicit guidance on when to use this tool versus alternatives, but the description implies it is for gauge charts and provides a prerequisite: 'SQL must return a VALUE column.' This is helpful but does not address alternative selection.

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