workload_handoff_take

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

The annotations declare readOnlyHint=true, yet the description explicitly states the statements "are then removed" once taken — a state mutation (one-shot consumption of the handoff buffer) that directly contradicts the read-only annotation. An agent relying on readOnlyHint would wrongly assume the operation is idempotent and safe to repeat.

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?

It is short, but brevity here comes at the cost of clarity: the single sentence is a noun fragment whose meaning depends on knowing the sibling tool. It is under-specified rather than efficiently concise, and the key action is not front-loaded.

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 one-param tool with no output schema and a minimal annotation set, the description should explain what is returned (a list of statements?), what the id looks like, and the single-use/error behavior. It omits all of this, leaving an agent unable to call it confidently.

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 one parameter (handoff_id) with 0% schema description coverage, so the description must carry the semantics. It only hints that the id relates to a handoff created by workload_handoff_put, adding no detail on format, how to obtain it, or what happens if it is invalid or already consumed.

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 does identify the resource it operates on ("the statements kept by workload_handoff_put") and implicitly names the sibling that creates them, which helps differentiate it from workload_handoff_put. However, it never states the action as a clear verb+resource pair — "take" is only in the tool name — and the fragment phrasing makes the purpose vague to an agent reading the description alone.

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?

The reference to workload_handoff_put and the "once: they are then removed" note imply a put-then-take workflow, but there is no explicit when-to-use statement, no prerequisite (e.g., a handoff_id created by put), and no alternative named. Usage must be inferred rather than read.

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