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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds a genuinely non-obvious behavioral trait: search terms or business capabilities may be forwarded to a third-party service (Cohere) to derive commodity filters. That kind of external data-flow disclosure is not derivable from schema or annotations, though pagination/result-shape behavior is still unaddressed.

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 sentences, front-loaded with the core action and no filler. The privacy/Cohere sentence is short and relevant, though it slightly displaces the usage guidance an agent would find more actionable.

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 4-parameter, all-optional search with full schema coverage and no output schema, the description covers the what and a privacy caveat but omits selection context relative to the crowded sibling set (find_alberta_opportunities, search_opportunities, find_matching_opportunities). Adequate but leaves a real routing gap.

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%: limit (default/max), status (default), category (services/goods/construction), and keywords are all documented in the schema. The description adds no format, syntax, or defaulting detail beyond that, 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?

States a specific verb and resource: 'Search Alberta Purchasing Connection opportunities from Alberta public-sector buyers', which is clear about the data source. However, it does not differentiate itself from closely-named siblings like find_alberta_opportunities, find_matching_opportunities, or search_opportunities, so an agent cannot tell which of these to pick from the description alone.

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?

No when-to-use guidance, no conditions that distinguish it from the many other opportunity-search siblings, and no exclusions. The only extra sentence concerns Cohere data transmission and a privacy pointer, not selection criteria.

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