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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, covering safety and side-effect-free behavior. The description adds useful behavioral context: that bid prices are included only 'where GSE has published them' (a data completeness caveat) and that results are available in English and Georgian. These details go beyond the annotation fields and inform the agent about limitations and output language.

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 description is a compact two-sentence structure. The first sentence front-loads the primary purpose and content, while the second adds language availability. Every phrase earns its place, with no fluff 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?

There is no output schema, so the description compensates by describing return contents (awarded bidder, contract reference, bid prices). It also explains the language options and the conditional availability of bid prices. Pagination and filtering details are in the schema, so they need not be repeated. The description is sufficient for an agent to understand the tool's scope and invoke it correctly.

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%, with all 4 parameters (lang, page, per_page, year) fully described in the input schema. The description adds minimal parameter-level detail beyond what the schema provides; it only mentions language availability, which echoes the 'lang' enum. Per the rubric, a baseline of 3 is appropriate when the schema carries the parameter documentation.

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 clearly states the tool provides procurement tenders from JSC Georgian State Electrosystem, listing specific content (awarded bidder, contract reference, bid prices). This distinguishes it from sibling tools like gse_publications or gse_grid_now, which cover other GSE data. The verb 'Procurement tenders' plus resource specification makes the purpose unambiguous.

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 description implies usage: it is for tender data from GSE, with language options. It gives clear context about what the tool offers but does not explicitly name alternatives or state when not to use it. Sibling tools like gse_publications could be confused, but the focus on tenders and specific content provides sufficient guidance for selection.

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