Advanced Database Query

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

With no annotations, the description carries the full burden. It implies a read-only query operation but does not explicitly state that it is non-destructive, nor does it mention rate limits, authentication needs, or other behavioral traits. It adds minimal value beyond the 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 sentence that efficiently enumerates key capabilities without extraneous words. It is front-loaded and fits within a standard length.

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?

While an output schema exists (reducing need to describe returns), the description lacks details on parameter usage, constraints, or error conditions. Given the tool has five parameters with no schema descriptions, more information would improve completeness. It is minimally adequate.

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%, so the five parameters have no inline descriptions. The description lists 'custom filters, field selection, pagination, and sorting options,' which loosely map to filter_dict, projection, skip/limit, and sort respectively, providing some semantic link. However, it does not explain parameter formats or constraints, leaving gaps.

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 it performs sophisticated searches with custom filters, field selection, pagination, and sorting, indicating a general-purpose query tool. However, it does not explicitly differentiate itself from sibling tools like search_by_name or bbox_search, which could lead to ambiguity.

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. The description lacks context about scenarios or prerequisites, leaving the agent to infer usage without explicit direction.

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