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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false). Beyond that the description adds real value: default ordering is closing-soonest, keyword supports Amharic, and it warns that each tender has published_at and should not be called 'new' without it. It does not cover pagination or result volume, but the field list substitutes for a missing output schema.

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?

Purpose and data source are front-loaded, then scope defaults and search modes. Two dense sentences with little waste, though the organisation-type list (banks, government, NGOs, World Bank) is more colour than actionable signal.

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 enumerates returned fields (issuing organisation, subject, deadline, days left, budget, source link) and states default sort and closed-tender behaviour. An agent could call this correctly; only pagination/limit behaviour is left purely to the schema.

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 the schema already documents all five parameters in detail. The description echoes the keyword/category semantics but adds little the schema does not already say (it omits limit and barely mentions include_closed's effect). Baseline 3 applies.

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 and resource (listing public tender notices) with the data source (BinaSmart, bina.et/tenders) and the exact fields returned. It is clearly distinguishable from siblings get_tender and list_tender_categories.

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?

It states the default scope (open tenders only unless include_closed is set) and the two search modes (keyword in English or Amharic, category filter), and the schema points to list_tender_categories as the enumeration helper. It stops short of explicitly routing single-tender lookups to get_tender.

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