search_drefs_by_country

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

No annotations are provided, so the description carries full burden. It only states the basic action and filter criterion, but does not disclose behavior such as result ordering, pagination (despite limit parameter), whether all DREF statuses are included, or any authentication requirements. This is a minimal behavioral disclosure.

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, clear sentence with no filler. It is appropriately sized for a simple search tool and front-loads the key action and filter.

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?

The tool has only 2 parameters and no output schema, so complexity is low. However, the description does not clarify whether this search returns all DREF statuses or only a subset, which could be ambiguous given sibling tools for completed/ongoing. It is minimally complete but leaves some contextual gaps.

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 parameters are already well-documented. The description adds no new meaning beyond restating the country_iso filter (by country ISO code). It does not clarify behavior of the limit parameter beyond schema defaults, 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 states the tool finds DREF operations by country ISO code, using a specific verb and resource. It distinguishes from siblings like search_drefs_by_disaster_type (different filter) and get_completed/ongoing_drefs (status-based).

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 implies usage for country-based searches but does not explicitly mention when to use this tool versus alternatives like search_drefs_by_disaster_type or get_ongoing_drefs. No exclusions or alternative tools are named, leaving the user to infer from sibling names.

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