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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds meaningful non-obvious behavior: the brief is free, search terms/capabilities may be transmitted to Cohere, and a privacy link is provided — exactly the kind of third-party/rate/data-handling context annotations cannot express.

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, purpose front-loaded, with the Cohere/privacy caveat placed last where it belongs. No filler, though the profile-override sentence duplicates schema content.

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?

No output schema exists, so the description carries some burden for explaining the return value, and it only vaguely implies a 'brief' with sections implied by `limit` ('Maximum items per section'). A nested `profile` object plus no described output structure leaves the returned shape under-specified for an agent.

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/profile are already documented in the schema, and the description largely restates the profile-override behavior that the schema already states ('Overrides any saved profile'). It adds marginal value beyond the structured fields, so baseline 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?

The description opens with a specific verb and resource ('Generate a free daily bid brief') and names the two data sources (CanadaBuys, Alberta APC) plus the input that drives it (a business profile). This distinguishes it from generic searchers like search_opportunities, though it never explicitly names a sibling alternative.

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 tells the agent to pass an inline `profile` per call, which is genuine usage guidance, but there is no explicit when-to-use-this-vs-alternatives statement (e.g. vs find_matching_opportunities or get_my_profile). Usage is implied by the 'daily brief' framing rather than stated.

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