create-search

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

With no annotations, the description carries full responsibility for behavioral disclosure. It mentions optional webhook notifications but does not explain that this persists a resource, the need for authentication, how webhooks are triggered, or what the return payload looks like. Key behavioral traits are missing.

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 two short sentences, front-loaded with the core action. Every phrase adds meaning, and it avoids redundancy or fluff, making it highly concise for a tool with 40 parameters.

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 tool with 40 parameters, no output schema, and no annotations, the description is too high-level. It doesn't mention that all parameters are optional, what the response will be, or any important side effects or constraints. It leaves the agent without critical context for correct invocation.

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 baseline is 3. The description groups parameters into location, price, size filters, and webhook endpoints, which adds a helpful conceptual structure but doesn't explain individual parameters beyond what the schema already provides.

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 creates a saved search, with a specific verb and resource. It distinguishes from sibling read/search tools by emphasizing creation and optional webhook notifications, though it doesn't explicitly compare with update-search or delete-search.

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?

No guidance is provided on when to use this tool versus alternatives like search-properties for immediate results or update-search for modifying existing searches. The description focuses purely on what the tool does, not on selection criteria.

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