apex_add_chart_drilldown

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

Annotations are all false, providing no safety or idempotence hints, so the description must carry the transparency burden. The one-sentence description does not disclose side effects such as page mutation, dependency on existing regions, or failure behavior if prerequisites are unmet.

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, front-loaded sentence that conveys the core action in a compact format. Every word is useful, with no redundancy or unnecessary detail.

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 tool with 6 parameters and a non-trivial workflow, the description is too minimal. It doesn't mention that the chart and IR regions must already exist, the auto-prefixing of item names, or that this modifies page metadata. Although the schema fills some gaps, the description itself lacks enough context for an agent to know when and how to invoke it correctly.

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 covers all 6 parameters with rich descriptions (e.g., target_item_name auto-prefix, filter_column informational), and description coverage is 100%. The main description adds no parameter-level meaning, so the baseline 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 clearly states the action ('Add chart drilldown') and the specific workflow (click chart series → set hidden item → refresh IR). This distinguishes it from sibling tools like apex_add_jet_chart or apex_add_dynamic_action by naming the drilldown behavior explicitly.

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 any prerequisites, exclusions, or alternative approaches. The only usage hints are in the schema descriptions for chart_region_name and target_region_name, which state the regions must already exist, but this is not in the main description.

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