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

No annotations are provided, so the description carries the full burden. It discloses a result cap ('Up to 100'), which is useful, but says nothing about authentication requirements for access_token, read-only semantics, ranking, or what 'open' means temporally.

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 single sentence is compact and front-loaded with the distinguishing 'PRO' tag, but 'PRO' is unexplained and the extreme brevity leaves no room for the information an agent actually needs.

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 annotations, no output schema, and only 25% schema description coverage on a 4-parameter tool, the description is far too thin to fill the gaps—nothing on result shape, auth, pagination, or how the 100-item cap interacts with the filters.

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 25% and the description merely restates the parameter names keyword, category, and region without adding accepted values, matching behavior, or format. Only access_token has a schema description, so the filter parameters remain semantically undefined in both places.

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 names the resource (open tenders) and the filtering dimensions, and the 'PRO' prefix hints at a premium tier versus the sibling tender_search. But it omits an explicit verb and never states how this differs functionally from tender_search, leaving the agent to guess whether it is the same search with a larger cap.

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?

There is no when-to-use guidance, no exclusion of alternatives, and no mention of the three sibling tools (closing_soon, new_since, tender_search) despite the near-identical name tender_search. The only implicit signal is 'PRO', which is unexplained jargon.

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