apex_add_bubble_chart

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

Annotations are all false, so the description carries the full burden of behavioral disclosure. It only mentions the SQL column mapping and does not disclose page-modifying effects, prerequisites, or what happens to existing regions. No contradiction with annotations exists, but the update-like nature is under-explained.

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 concise: two short clauses that fit on one line, front-loaded with the main action. Every word earns its place, and there is no redundancy.

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 rich input schema and presence of an output schema compensate somewhat for the minimal description. However, the description lacks contextual guidance about when to choose a bubble chart over alternatives, prerequisites, or relational constraints, so an agent must rely entirely on the tool name and schema.

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 description coverage is 100%, so the baseline is 3. The description's 'SQL: X_VALUE, Y_VALUE, BUBBLE_SIZE, optional LABEL' adds a concise conceptual mapping to x_column, y_column, z_column, and label_column parameters, but the schema already provides detailed parameter descriptions, so the added value is marginal.

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 'Add a bubble chart' with a specific verb and resource, making the core purpose obvious. However, it does not explicitly differentiate from sibling chart tools like apex_add_scatter_plot, relying primarily on the tool name for distinction.

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?

Usage is implied by the name and one-line description, but there is no explicit guidance on when to use this tool versus alternatives. Given many chart-related siblings, no selection criteria are provided, leaving the agent to infer that a bubble chart is simply a chart type.

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