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 covered. The description adds genuine value beyond that: it discloses that search terms or business capabilities may be sent to a third party (Cohere) for commodity filter selection, and points to /privacy, which is a meaningful data-handling disclosure an agent should know.

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?

Three sentences, front-loaded with purpose and then the key usage and privacy notes; little waste. The /privacy pointer is terse but purposeful. Slightly more compaction is possible but structure is good.

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 output schema and a nested-object profile, the description never says what the returned opportunities look like (fields, ordering, count behavior). Parameters are well covered by the schema, so the main gap is return-value expectation, which for a search tool an agent would benefit from knowing.

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%, so days, limit, and the nested profile fields are already documented in the schema. The description adds only marginal meaning — the per-call override semantics and the Cohere-derived capabilities — so the baseline of 3 is appropriate.

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 ('Find Alberta Purchasing Connection opportunities') and adds a matching criterion tied to the business profile, so the agent knows what it retrieves. It does not distinguish itself from close siblings such as search_alberta_opportunities, find_matching_opportunities, or find_opportunities, which an agent could easily confuse it with.

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?

It implies when to use the inline `profile` ('the way to describe your business' on the public endpoint) but gives no explicit when-to-use vs. when-not guidance relative to the many sibling search/find tools. Usage is inferable from the profile-override note rather than stated.

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