apex_add_percent_bars

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

All annotations are false, so the description must disclose behavioral traits. It only says 'Add' without addressing side effects, permission requirements, or what happens if the region already exists. The mention of 'max' in the description but not in the schema creates confusion about behavior.

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, but the 'Each: {label, value, max, color}' phrase is cryptic and not a clear list of actual parameters. It is brief but slightly opaque, earning a 4 rather than a 5.

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?

For a mutation tool with 9 parameters and an output schema, the description is severely underspecified. It lacks usage scenarios, prerequisites, and a clear data contract for the SQL query. The output schema covers return values, but the description fails to tie the input parameters to the visual output, especially the 'max' concept.

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?

While schema coverage is high (89%), the description adds a 'max' field that has no corresponding schema property, which is misleading. It does not clarify how sql_query maps to label/value columns beyond the schema's own descriptions, and the structure '{label, value, max, color}' does not align with the actual parameters.

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 horizontal percent bars' with a clear verb and resource, making the tool's action obvious. The 'Each: {label, value, max, color}' snippet further clarifies the bar structure, and the name itself distinguishes it from sibling chart tools.

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 is provided on when to use this tool versus alternatives like apex_add_jet_chart or apex_add_metric_cards. There are no prerequisites, exclusions, or contextual hints for selecting percent bars.

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