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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond the annotations: the host requirement (sign-in plus an active workspaceAlberta Pro subscription) and the sort order and returned fields.

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, zero waste, and the core action is front-loaded before the hosted-prerequisite note. Every clause earns its place by adding sorting, field, or auth information.

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?

There is no output schema, so the description usefully compensates by naming what is returned (closing date sort, days remaining, notes). With no parameters and annotations covering safety, the only minor gap is that no pagination or result-size behavior is mentioned.

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?

The tool takes zero parameters, so per the calibration baseline this scores 4. The schema is empty with 100% coverage, and the description correctly adds no parameter claims that would conflict.

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 verb and resource ('List watched opportunities') and adds scope detail (sorted by closing date, includes days remaining and notes). The watchlist resource is unique among the siblings (watch_opportunity/unwatch_opportunity are mutations of it), so an agent can identify this read-only listing without ambiguity.

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?

Usage is only implied: an agent can infer this is the way to view items the user previously saved, but there is no explicit statement of when to use this versus siblings like list_deadlines, find_opportunities, or get_opportunity_details, and no exclusions are given.

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