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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful behavioral context beyond annotations: it is 'free', 'daily', pulls from CanadaBuys and Alberta APC, and the profile is per-call (inline). This informs the agent that no persistent profile is used, which is valuable for expected behavior.

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 short sentences, front-loaded with the core purpose and followed by the key usage instruction. Every word earns its place; no filler or redundancy. The structure is efficient and easy to scan.

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 read-only tool with 100% schema coverage, the description covers the core purpose and the key behavioral nuance (inline profile). It does not describe the output format or sections, but given no output schema and the straightforward nature of a 'brief', it is sufficiently complete for an agent to invoke correctly. A minor gap is not explaining how days/limit affect the output, though the schema covers them.

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 100%, so the baseline is 3. The description mentions passing an inline profile 'per call', but this is already stated in the schema's profile field description ('used for this call only'). The description does not add extra meaning for days or limit beyond what the schema provides, so it does not exceed the baseline.

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 action ('Generate') on a specific resource ('a free daily bid brief') with explicit data sources (CanadaBuys and Alberta APC). This clearly distinguishes it from sibling tools like search_opportunities or find_matching_opportunities, which are search-oriented rather than brief-generation tools.

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 description implies usage for generating a daily brief and mentions it is for a business profile, but it does not explicitly contrast with alternatives or state when not to use this tool. It gives some context (free, daily, from specific sources) but lacks explicit routing guidance among the many siblings.

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