create_search

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

Annotations already convey idempotency, non-read-only, and non-destructive behavior. The description adds the precondition to consult GET/schema first, which is contextual value, but it does not describe side effects, required permissions, or what happens on success. No contradiction with annotations exists.

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 compact and front-loaded: a purpose statement, the concrete endpoint, and an argument note. Every line contributes actionable information without filler or 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?

For a one-parameter create call with an output schema and helpful annotations, the description supplies the endpoint and a clear path to discovering the body structure. The main gaps are not explaining how this differs from create_search_bulk and not describing expected response behavior, though the output schema helps fill part of that.

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 single body parameter has no schema documentation and is additionalProperties, yet the description identifies it as the request payload and directs the agent to the authoritative GET/schema endpoint for field details. This meaningfully compensates for the opaque 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 states a clear create operation on a search resource and provides the endpoint POST /api/v1/search. However, it does not distinguish this from sibling create_search_bulk, so purpose is clear but lacks sibling differentiation.

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 useful precondition: read the matching GET or /schema endpoint before supplying a body. It does not, however, state when to prefer this tool over alternatives like create_search_bulk, nor does it mention exclusions or when not to use it.

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