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 adds genuinely useful context beyond that: a 20-result cap and the id naming scheme (tender:<reference_no>, agency:<id>, company:<id>, report:<YYYY-MM>) that tells the agent what kinds of entities come back.

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 definition is compact and front-loads the resource scope before the return-shape and query tip. The bilingual duplication (Arabic sentence followed by an English gloss) is slightly repetitive, but each element is short and earns its place.

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 correctly compensates by describing the return format (up to 20 results of {id, title, url}) and id encoding. It stops short of explaining pagination or how to retrieve more than the 20-result cap, which would help for a search tool.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines 'query'. The description adds a real semantic hint beyond it — that Arabic keywords match better — which is actionable guidance the schema does not carry.

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 states a clear verb (search) and enumerates the resources covered: Saudi government tenders from Etimad, agencies, companies, and monthly reports. This implicitly distinguishes it as the broad, cross-entity search versus the narrower sibling search_tenders, though that contrast is never made explicit.

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?

Usage is only implied: the multi-entity scope suggests it is the general-purpose search entry point, and 'Arabic keywords match best' hints at query phrasing. There is no explicit when-to-use versus search_tenders/fetch and no exclusions, leaving selection between the two search tools to inference.

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