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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the return contract: counts, open-now tenders, top activities, top winning companies, and page URLs. Since no output schema exists, disclosing the payload is genuinely useful. It does not cover pagination, freshness, or behavior for unknown agency names.

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?

Two sentences, front-loaded with the Arabic definition followed by the English gloss; the enumeration of returned fields is dense and earns its space. The cost is bilingual duplication of the same content, which slightly inflates length without adding information.

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?

For a one-parameter read-only summary with no output schema, the description supplies what an agent needs to call it and what to expect back. The remaining gaps — no alternative routing and no handling of ambiguous or missing agency names — are minor for this tool's complexity.

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% and the single parameter's meaning ('agency name (Arabic) or id') is already fully documented in the schema. The description restates the same Arabic-name-or-id input without adding format, lookup, or ambiguity-resolution detail, so 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 (summarize) and resource (a Saudi government agency), and enumerates the payload: tender counts, open-now tenders, top activities, top winning companies. A sibling company_summary exists but the description never names it or contrasts the two, so differentiation is inferred from the resource noun rather than stated.

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 — an agent can infer 'call this to profile an agency', but there is no when-to-use/when-not guidance and no mention of company_summary, market_report, or search_tenders as alternatives. The only explicit instruction is the input form ('by name or id').

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