memo_handoff_create

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

Annotations provide little behavioral hint (all false). The description adds 'durable' implying persistence, but gives no details on side effects, idempotency, or what 'handoff' entails. With annotations carrying minimal weight, the description partially fills the gap but not fully.

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?

The description is only one sentence, which is concise but overly brief. It front-loads the core idea, but at the cost of necessary explanatory content. A middle score reflects the balance.

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?

Despite having an output schema (signaled but not shown) and 4 parameters with zero description coverage, the description omits any details about return values, parameter semantics, or behavioral nuances. It is incomplete for a creation tool expected to produce a resource identifier or status.

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%, yet the description provides no information about any parameters (project, summary, to_actor, from_actor). It fails to add meaning beyond the schema, leaving the agent to guess their roles.

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 clearly states the action (create) and resource (durable handoff) and targets (another agent or session). It is specific enough to distinguish from most sibling tools, though it could explicitly contrast with memo_handoff_consume.

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 guidance on when to use this tool versus alternatives like memo_handoff_consume or other memo tools. Missing context on prerequisites or typical use cases.

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