apex_add_stacked_chart

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

Annotations are all false, offering little behavioral context. The description only says 'Add' without disclosing whether this creates a new region, modifies the existing region, replaces series, or requires specific permissions. It adds no meaningful behavioral information beyond the action itself.

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 extremely short and front-loaded with the main action. The 'SQL: LABEL, VALUE, SERIES' fragment is terse but not wasteful. However, it is cryptic enough that it doesn't fully stand alone without the schema.

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?

With 13 parameters and an output schema not shown in the input, the description is too sparse to give an agent a complete understanding. It doesn't explain how page_id, region_name, and series_list interact, nor the overall workflow of the tool. This is a significant gap for a complex 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?

The input schema has 100% coverage, with descriptions for every parameter, so the baseline is 3. The description's 'SQL: LABEL, VALUE, SERIES' adds a minor summary of the series_list structure but provides no new semantics beyond what the schema already describes.

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 action: 'Add a stacked bar/column chart.' It uses a specific verb and resource, and the 'stacked' qualifier distinguishes it from other chart tools. However, it doesn't explicitly differentiate it from similar chart types like area or combo charts.

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 provides no guidance on when to use this tool versus alternatives. It does not mention use cases, prerequisites, or exclusions. An agent comparing many chart-addition tools gets no help in deciding if a stacked chart is the right choice.

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