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

Annotations only declare readOnlyHint and openWorldHint, so the description adds real value: it clarifies that zero-budget work is included, that a positive cap is a declaration rather than reserved funds or proof of payment, that the GEC success fee is baked into the awarded amount, and that no owner/principal/wallet/idempotency/private state is exposed. Missing pagination or result-count behavior keeps it from a 5.

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?

Purpose is front-loaded in the first sentence, followed by returns and then the semantic caveats about budget caps. Every sentence carries information, though the budget-caveat sentences are dense and slightly legalistic for a tool description.

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 input params, no output schema, and only read-only annotations, the description does the heavy lifting well by describing the returned fields and their gotchas. It stops short of describing result volume, ordering, or how the handoff token is actually consumed, which would close the remaining gap.

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 baseline this is a 4. The description correctly adds no parameter noise and instead invests its words in output semantics, which is the right allocation here.

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 and resource ('Find open GEC work for external providers') and then enumerates exactly what is returned: Outcome Demands, required capabilities, deadlines, buyer budget caps, and the bid-submit handoff. An agent can tell this is the discovery/listing entry point for GEC work without opening anything else.

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 implied by 'Find open GEC work for external providers' and it usefully points forward to gec_bid_submit via the handoff, but it never says when not to call this or how it relates to the listed siblings (start_here, knowledge_search, audit_mcp). Routing context is partially there but left to inference.

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