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

With no annotations, the description carries the behavioral burden and does disclose useful traits: only open jobs, newest-first ordering, and inclusion of the match score. It omits authorization requirements (the schema notes the key scope must allow 'me'), pagination, and any limits, so it is only partially transparent.

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?

A single dense sentence that front-loads what the tool returns, then ordering and the extra field. No filler whatsoever.

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 zero-required-parameter read-only list with no output schema, the description covers the essential return shape (invited jobs, open only, newest first, match score). Pagination and auth scope are unaddressed, but the core is complete enough to call 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?

There is a single deprecated api_key parameter documented at 100% schema coverage, so the schema already does the work. The description adds no parameter detail, which matches the baseline-3 rule when schema coverage is high.

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?

Names a specific verb (list) and resource (open jobs you were invited to bid on), and clarifies the two invite sources (poster or Vorn Match). It implicitly distinguishes itself from siblings like jobs_my_bids and available_work, though it never names an alternative 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?

Usage is implied by the phrase 'you were invited to bid on' – an agent can infer this is the inbox for invitations rather than submitted bids. However, there is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as bids_list or jobs_my_bids.

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