apex_add_funnel

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

All annotations are false, so the description carries the full burden. It discloses a key behavioral requirement (SQL alias and ordering), but does not mention side effects, permissions, or what happens upon completion. The addition of the SQL constraint provides some transparency, but it is minimal for a mutation tool.

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 sentence with no filler. It front-loads the primary action and then gives the essential SQL requirement. Every word earns its place.

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 tool has nine parameters and moderate complexity. The description gives the critical SQL requirement but lacks context on when to use it compared to other chart tools or what the resulting page change looks like. The presence of an output schema mitigates some ambiguity about return values, but for a mutation tool with neutral annotations, a bit more context would be helpful.

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%, so the baseline is 3. The description adds the explicit alias requirement for LABEL and VALUE, which is already implied by the schema example and label_column/value_column defaults. It provides marginal added meaning beyond the schema.

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 begins with 'Add a funnel chart,' which clearly states the specific verb and resource. It also includes a distinctive SQL requirement that differentiates it from sibling chart tools like apex_add_jet_chart or apex_add_gauge.

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 gives a clear usage constraint: 'SQL must alias LABEL + VALUE ordered by sequence.' This tells the agent when the tool is applicable and what prerequisites must be met. However, it does not explicitly mention alternatives or when not to use it, so it falls short of a 5.

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