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

Annotation contradiction: readOnlyHint=true claims the tool makes no environment changes, but the description says it records a decision and performs 'queue bookkeeping,' which is a state-changing operation. idempotentHint=false also suggests non-read-only behavior. Per the rubric, a description contradicting annotations receives a 1.

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 tight sentences with no filler. The purpose and decision values are front-loaded, and the side-effect exclusions are compactly listed in the second sentence.

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 10-parameter tool with a rich schema and an output schema, the description supplies the essential high-level context and safety boundary. It does not explicitly explain send/apply semantics or tenant_id, but those are optional and largely covered by the closed-world caveat. The main remaining completeness issue is the conflict with readOnlyHint.

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 70%, and the schema already documents the decision enum, queue_item_id, title/company lookup, reason, revisit_after, and actor_id. The description adds a useful closed-world caveat that helps interpret the send/apply booleans, but it does not explain their actual meaning or the lookup fallback mechanics beyond what the schema provides.

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 specific action and resource: 'Record the account owner's manual decision on an existing Talent Scout queue item.' It enumerates the exact decision values and explicitly labels the tool as 'closed-world queue bookkeeping only,' which distinguishes it from sibling outreach and application tools.

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?

It clearly says when to use the tool: to record an owner's manual decision on an existing queue item. It also provides an explicit when-not list: it 'never sends outreach, applies, clicks, submits, screens people, ranks people for hiring, or contacts anyone,' preventing an agent from using it for external actions.

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