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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world behavior, so the safety profile is covered. The description adds genuinely non-structured context: the authentication requirement, the key's source (MCC portal Security tab) and the exact header format 'Authorization: Bearer mccv_...'. It stops short of describing return shape or pagination, but the parenthetical field list partially compensates.

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 compact sentences: the first front-loads what is returned, the second front-loads the prerequisite. No filler. Minor deduction for the truncated token prefix ('mccv_...') which looks clipped rather than deliberate.

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-parameter read tool with no output schema, the definition covers purpose, returned entities, and the full authentication prerequisite, which is the main failure mode an agent would hit. It would be stronger with a note on ordering, volume limits, or what an empty list means, but nothing critical is missing.

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 the baseline is a 4. The description correctly conveys that the call is scoped implicitly by the bearer token rather than by arguments, which is a meaningful clarification for an argument-free tool.

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 and scope: the contractor's own open job offers (with fields area, time, pay, distance) plus their active jobs. The possessive 'my' distinguishes it from sibling tools that act on offers (vendor_respond_offer, apply_as_vendor), 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?

'For an MCC contractor's own assistant' implies the caller persona and context (fetching one's own pipeline rather than acting on an offer), which is a useful usage signal. However, there is no explicit when-to-use vs when-to-use-something-else guidance and no statement about what to do if there are no offers.

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