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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is largely covered. The description adds nothing beyond them: it does not say which actions are destructive (award_offer/cancel_gig likely mutate, list_board/list_offers read), nor that permissions or award preconditions may apply. With annotations carrying the burden, the description leaves behavior essentially undisclosed.

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 short sentence with no filler, but it is under-specified rather than concise for a six-action polymorphic tool. Its size is disproportionate to the complexity it must convey, so brevity is a liability here.

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 destructive, non-idempotent, action-dispatched tool with an opaque nested params object and no output schema, the description is completely inadequate. It omits per-action parameter contracts, mutation semantics, and return information that nothing else in the definition supplies.

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% and the 'params' property is an unconstrained nested object with no documented shape. The description gives no mapping between each of the six actions and the fields params must contain, which is the single most important thing an agent needs here. It adds no meaning beyond the bare enum.

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 resources (job board gigs, offers, bids, awards) but uses a vague catch-all verb, 'Manage', that does not tell an agent what the tool actually does. It does not name any of the six actions (post_gig, make_offer, award_offer, cancel_gig, list_board, list_offers) or distinguish this tool from siblings like handoff_task or handoff_work. Purpose is inferable from the name and noun list only.

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?

There is no guidance on when to use this tool versus the many handoff_* siblings, and no indication of which action to choose for a given intent. 'Bids' is mentioned in the description but has no corresponding enum action, which adds confusion rather than routing help. The agent must reverse-engineer usage from the enum alone.

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