apex_add_faceted_search

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

The description does not disclose behavioral side effects, such as whether existing filters are replaced or if any page re-render is required. Annotations indicate it is not read-only, but no additional context about destructive potential or permissions is provided.

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, using a compact format to convey the essence of the tool without unnecessary words. The schema carries the detail, making this appropriately sized and well-structured.

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?

Within the context of the rich schema and annotations, the description is adequate for understanding the tool's primary purpose, but it lacks information about prerequisites or side effects. Since an output schema is present, return values are covered elsewhere.

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 provides 100% coverage with detailed descriptions, especially for the facets array. The description's mention of facet structure mirrors the schema but adds no new information beyond what is already documented.

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 tool adds faceted search, specifying that it filters SELECT_LISTs and IR. It distinguishes from sibling tools like apex_add_search_bar by its specific focus on facets.

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 implies use when adding facet-based filtering to IR pages with SELECT_LISTs, but it does not explicitly contrast with alternatives or state exclusions. There is no mention of when not to use it or prerequisite conditions.

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