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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuinely useful context beyond them: this is a static/planned source listing, not live opportunity data. It does not say what the response contains (names, URLs, planned phases?) or whether results are filtered by the input.

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 tight sentences, with the scope and the important 'not yet indexed' caveat front-loaded. The trailing vendor attribution and URL are boilerplate that does not help an agent decide or invoke, costing a point.

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-optional-parameter read-only listing with no output schema, the description covers the essentials plus the critical caveat that the data is a planned/pointer list. The main residual gap is the unfiltered meaning of the 'level' parameter and what the returned entries look like.

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 0% for the single 'level' enum parameter, so the description must compensate, and it only partially does: the enumerated levels listed (federal, California, Santa Clara County, City of Santa Clara) map implicitly onto federal/state/county/city. It never says that 'level' filters the list or what happens when omitted.

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 names a specific resource (official government contract-opportunity sources) and scopes it to four buyer levels (federal, California, Santa Clara County, City of Santa Clara). It also states the tool's nature as a directory rather than a search index. It does not differentiate from any sibling by name, so it falls short of a 5.

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 gives implicit when-not-to-use guidance via 'Datamart does not index opportunities yet (Phase B); this lists where to look and what is planned' — telling the agent not to expect actual opportunity records. However, it names no alternative tool for actually finding opportunities and gives no explicit trigger conditions for calling this versus another list tool.

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