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

Annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description adds real behavioral context beyond that: result cap ('up to 10 live tenders'), freshness ('refreshed daily'), source ('official procurement portals'), and returned fields (buyer, deadline, value, askTender link).

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?

Three sentences, front-loaded with purpose, then return shape, then trigger condition. Every clause carries information (cap, freshness, source, fields, use case) with no filler or repetition.

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 covers what comes back (buyer, deadline, value, link) and the 10-result ceiling, which is the key expectation-setting detail. Minor gaps remain: no mention of what an empty result set looks like or whether results are ranked, but nothing essential to correct invocation is missing.

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 coverage is 75% and the query/country/closing_within_days params are already well described in the schema. The description's 'by what is being bought and, optionally, the country' and 'up to 10' merely restate what the schema declares, adding no syntax, format, or edge-case detail (e.g. multi-country input, behavior when no results match).

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 ('Find open government tenders (calls for bids)') plus the primary scope ('by what is being bought and, optionally, the country'). An agent can distinguish this public-tender search from siblings like my_saved_tenders, my_matching_tenders, and the single-item get_tender, though no sibling is named explicitly.

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?

Explicit trigger sentence: 'Use when the user asks to find tenders, calls for bids or public contracts to bid on.' It gives a clear when-to-use but offers no when-not-to-use guidance or named alternatives (e.g. use get_tender for a known ID, my_matching_tenders for personalized results).

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