work_pending_handoffs

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

No annotations are provided, so the description carries the full burden. 'Find' implies a read, but it never states whether this is read-only, what 'compact' or 'local' mean operationally, whether results are paginated, or who 'this agent' resolves to.

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 front-loaded sentence with no filler. It is efficient, though the brevity borders on under-specification rather than tight writing.

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?

An output schema exists, so return values need not be explained. But for a two-parameter tool with zero schema coverage and no annotations, the description omits the parameter meanings and behavioral profile an agent needs to invoke it 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 0% and the description does not clarify either parameter. 'Addressed to this agent' loosely gestures at to_agent but doesn't confirm it is the recipient identifier, and the project parameter is entirely unmentioned in both schema and description.

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 states a verb (find) and resource (handoffs) and adds a scope (addressed to this agent), so the basic operation is discernible. However, 'compact local' is unexplained jargon and there is no differentiation from the very similarly named sibling work_handoff, leaving the agent to guess how they relate.

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?

No when-to-use guidance and no mention of alternatives. With siblings like work_handoff, work_claim, and work_resume in the same family, an agent has no signal about when this retrieval tool is the right pick versus those.

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