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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description usefully adds the source aggregation and geographic boundary, but says nothing about rate limits, auth, or how results are ordered/paginated.

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?

One dense but well-formed sentence that front-loads the search action and resource types, then layers in scope, sources, and result content. No filler text.

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?

With no output schema, the description usefully notes the result payload (deadlines, sectors, links to the original notice). For a 6-parameter tool it still leaves parameter behavior (limit, open_only, country code format) partly to the schema, but the overall coverage is solid.

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 50%; the description loosely mirrors 'sectors', 'countries', and opportunity kinds but adds no syntax or defaults beyond the schema. It does not clarify the 'limit' cap or the open_only default behavior, so it only marginally compensates for the coverage gap. 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?

States a specific verb ('Searches') plus the exact resource types (RFPs, tenders, EOIs, grants), the geographic scope (Central America), and the named source corpus (World Bank, IDB, EU TED/Funding & Tenders, Grants.gov). This clearly separates it from siblings like search_news or search_legal without opening any schema.

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 corpus and geography imply the intended use case, but there is no explicit 'use this when…' or exclusion against alternatives such as browse_marketplace or search. An agent must infer the routing decision itself.

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