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

With no annotations, the description carries the full burden, and it does disclose two behavioral facts: the default window of 14 days and the sort order (soonest first). It omits the subscription/auth requirement implied by 'PRO' and the access_token parameter, and says nothing about return format or pagination, leaving real gaps for a read tool.

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 compact sentences with the scope and default front-loaded and no filler. The 'PRO.' prefix is terse but conveys a paywall signal efficiently.

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?

The description covers the time window and ordering but leaves the required profile parameter, the auth/subscription requirement, and the return shape unexplained for a tool with no annotations and no output schema. Adequate but with clear gaps.

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 50%, but the description compensates for the undocumented within_days parameter by stating its meaning and default (next N days, default 14). The required 'profile' array parameter remains completely undefined in both schema and description, which is a notable gap.

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 specific resource (matches with deadlines in the next N days) and adds scope and ordering (default 14, soonest first). It does not name the sibling tools (new_since, tender_match, tender_match_full), so the agent must infer when this is the right one.

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 'closing soon' concept plus the next-N-days window implies the use case (upcoming deadlines), but there is no explicit when-to-use or when-not clause and no reference to the sibling tools as alternatives. Usage is inferable but not spelled out.

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