Search Api Facet Create

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

No annotations are provided, so the description carries the full behavioral burden. 'Create' implies a mutation, but there is no information about permissions, side effects, uniqueness constraints, or whether the operation is reversible. It is only minimally more informative than a bare operation name.

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 short sentence with no wasted words, but it is under-specified rather than appropriately concise. It lacks the detail needed to help an agent invoke the tool correctly.

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?

Although an output schema exists and return values need not be explained, the description is completely inadequate for a 6-parameter create tool. It provides no usage context, no behavioral details, and no parameter semantics, leaving the agent with almost nothing beyond the tool name.

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 0% across 6 parameters, and the description does not mention any parameter names or meanings. Required fields such as id, label, index_id, and field, as well as optional settings and facet_type, are left entirely undocumented by the description. This fails to compensate for the coverage gap.

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 states a specific verb and resource: 'Create a Search API facet.' It clearly identifies the operation and the entity being created. However, it does not explicitly differentiate this tool from sibling operations such as search_api_facet_list or other create tools, so it stops short of a 5.

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 no guidance on when to use this tool, when not to use it, or what alternatives exist. It does not mention prerequisites such as needing an existing Search API index or server. There is only the implied action of creating a facet.

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