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

No annotations exist, so the description carries the full burden. It usefully discloses the PRO/subscriber gating and the 'open tenders' scope plus a concrete date format, but says nothing about result ordering, pagination, or what happens on an invalid date.

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?

A single tight sentence, front-loaded with the tier marker and the primary filter. The leading 'PRO.' is slightly cryptic but costs little.

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 3-param unannotated search tool with no output schema, the description covers scope and date format but omits return shape, ordering, and limits — enough to call it correctly, not enough to predict its output.

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 only 33%, so compensation was needed. The description does clarify the 'since' format (YYYY-MM-DD) and marks keyword as optional, which the schema leaves undocumented; access_token is covered by its own schema description. Still thin on keyword matching semantics.

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 (published on or after) and resource (open tenders), with the date format inline. It implies a filter-based search distinct from the sibling list, though it never names closing_soon or tender_search to sharpen the distinction.

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?

"for daily monitoring" gives a usage context, but there is no explicit when-to-use vs. closing_soon/tender_search guidance and no stated exclusions or prerequisites beyond the PRO gate.

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