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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds a genuine behavioral rule the annotations do not carry: a stale qualification cannot authorize a new submission, which tells the agent freshness matters regardless of a successful read.

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: the first delivers the payload contract, the second delivers the decision-relevant constraint. No filler, and the returned contents are front-loaded.

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?

With no output schema, the description carries the burden of describing returns and does so by listing qualification, revision, gaps and bid decision. Minor gaps remain (no error/empty-state behavior for a missing qualification), but it is sufficient to call the tool 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 projectId parameter, and the schema itself already warns it is a Helvabase project/mapping ID, never a local path. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

States a specific verb (Read) and resource (the current saved qualification) and enumerates what it surfaces: revision, unresolved gaps, and the email-confirmed bid decision. This is clear enough to distinguish it from write-side siblings like submit_qualification or confirm_bid_decision, though it never names the contrasting tool explicitly.

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 closing sentence ('A stale qualification cannot authorize a new submission') implies the tool is a prerequisite check before submitting, but it never states when to call this versus siblings such as read_bid_method or confirm_bid_decision. Usage is inferable rather than spelled out.

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