Search Estimates

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

Annotations already disclose that this is read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds only a filter list and does not disclose behavior like pagination, result ordering, match semantics, or how multiple filters combine. No contradiction with annotations.

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 compact sentence that front-loads the action and resource before listing filters. There is no filler or redundant explanation, though the long filter enumeration overlaps heavily with the schema.

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 15 optional parameters and no output schema, the description is somewhat thin: it does not explain what a successful response contains, how filters interact, or pagination behavior beyond the schema defaults. Strong annotations and full schema coverage mitigate the gap but do not fully replace missing operational 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 description coverage is 100%, so every parameter already has a meaningful description including match type and defaults for pagination. The tool description merely summarizes filter names and adds no semantic value beyond the schema, so baseline 3 is appropriate.

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 identifies the action ('Search') and resource ('estimates') and enumerates the main filter dimensions (status, customer, contact, address, category, source, PO number, dates). It is unambiguous, though it does not explicitly distinguish itself from siblings like get_estimate_details or search_jobs.

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 given about when to use this tool versus alternatives such as get_estimate_details for retrieving a single estimate or search_jobs/search_customers for other entity types. The description implies a list-style search but provides no when-to-use or when-not-to-use direction.

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