search_sightings

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

With no annotations, the description must carry full behavioral transparency. It only states 'Returns matching records (brief form)', omitting details about whether the operation is read-only, destructive, any authentication needs, rate limits, or pagination. The phrase 'brief form' is vague.

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 conveys the core purpose and search dimensions. Every word serves a purpose; no fluff or redundant information.

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?

Given the tool has 7 parameters, no output schema, and no annotations, the description is insufficient. It omits critical details like the 'limit' parameter behavior, result format details, and handling of empty results. An agent would lack enough context to use the tool effectively.

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 description covers 5 of 7 parameters (query, agency, type, location, year range) but omits 'limit' and does not explicitly name 'year_start' and 'year_end' (though implied by 'year range'). The schema already provides descriptions for most parameters, so the description adds marginal value. A 3 is appropriate given schema coverage >50%.

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 tool as a search over 'declassified PURSUE UAP records' with specific searchable dimensions (free text, agency, file type, year range, location). The verb 'Search' and resource are clear, but it does not differentiate from the sibling 'full_text_search', which may have overlapping functionality.

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 'full_text_search', 'get_sighting', or 'stats'. There are no examples or context for appropriate use cases, making it harder for an agent to choose correctly among similar siblings.

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