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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds only the aggregation scope across two procurement sources; it says nothing about ordering of deadlines, truncation behavior, or how combined results are interleaved, which are the traits that actually matter for this 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?

A single front-loaded sentence with zero filler, which is appropriately sized for a simple list tool. It is slightly under-specified rather than wasteful: 'closing soon' is never tied to the default 30-day horizon that the schema actually defines.

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 five optional params, a full output schema, and strong annotations, most invocation detail is carried by structured fields, so the description needs only routing context. The missing piece is exactly that: differentiation from list_upcoming_deadlines and list_alberta_deadlines, which share almost the same semantics.

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 every parameter (days, limit, source, category, province) is self-documented with defaults and enumerated-ish values, so the schema does the heavy lifting. The description adds no extra parameter meaning, so the 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?

The description gives a clear verb+resource (list opportunities closing soon) and names the two data sources, CanadaBuys and Alberta APC. However, it does not distinguish this tool from near-identical siblings such as list_upcoming_deadlines and list_alberta_deadlines, so an agent cannot tell from the description which one to call.

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 statement of when to use this tool, when not to, or which sibling to prefer. The only implicit signal is the 'CanadaBuys and Alberta APC' scope, which loosely maps to the source parameter, but a caller facing list_upcoming_deadlines has no textual reason to choose one over the other.

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