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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds 'Fast deterministic' and 'No model call', which discloses performance and execution behavior beyond the annotations. It also describes the verdict outcome ('go/caution/no-go verdict with reasons'), providing useful behavioral context.

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?

The description is two sentences with zero waste. It front-loads the purpose and criteria, then adds a final clarifying note about determinism. Every clause earns its place, making it an exemplary concise definition.

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 single-parameter, read-only tool with no output schema, the description covers the essential context: what it does, what criteria it evaluates, and the nature of the verdict. It leaves out the exact output format, but the lack of an output schema and the simplicity of the tool make this acceptable. The description is complete enough for an agent to call it correctly.

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% for the single parameter 'reference' with a description of 'CanadaBuys or Alberta APC reference number'. The tool description repeats 'for one opportunity' but does not add any new semantic detail about the parameter (e.g., format or validation). Baseline of 3 is appropriate as the schema fully documents the parameter.

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 clearly states a specific verb (assess) and resource (bid/no-bid checklist for one opportunity), and lists the evaluation criteria. It is unambiguous and unlikely to be confused with sibling tools, though it does not explicitly name a sibling to differentiate from.

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 a single opportunity ('for one opportunity') but provides no explicit guidance on when to use this tool versus alternatives like daily_bid_brief or get_opportunity_details. No exclusions or alternative-referencing is present, leaving the agent to infer selection.

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