apex_add_icon_list

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

The description only states 'Add an icon list' without disclosing that it likely creates a region on a page, requires a SQL query, or has any side effects. Annotations provide no helpful hints (all false), so the description carries the burden but fails to explain the operational 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 very brief, which is generally good, but it omits essential information about the tool's operation. It is compact but under-specified, failing to earn its place by conveying only a minimal idea of the tool's function.

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 10 parameters, 3 required, and a core SQL query input, the description is inadequate. It does not explain how the SQL query drives the icon list, what the optional columns do, or how the agent should populate fields correctly. An output schema exists, but that does not compensate for the lack of usage context.

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 high (90%), but the description misrepresents the parameter structure by mentioning 'description' which is not a schema property, and by suggesting items are defined as {icon, label, description, page_id} when the schema uses label_column, value_column, and icon_column. This adds confusion rather than clarifying how to set the required sql_query.

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 uses the verb 'Add' with the resource 'icon list', indicating a specific action. However, it does not differentiate from sibling tools like apex_add_quick_links or apex_add_metric_cards, and the phrase 'Each: {icon, label, description, page_id}' is confusing because page_id is a top-level parameter, not an item property.

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?

There is no guidance on when to use this tool versus other add_* tools. No context is provided about appropriate use cases, prerequisites, or alternatives, leaving the agent without decision support.

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