Create private mark

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

Description adds significant behavioral context beyond the annotations: it reveals the write location (.notch/private/inbox/), states the packet is never sent anywhere, and notes it stays hidden from packet listings unless --include-private is passed. This is meaningful transparency for a write operation, going well beyond the annotations.

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 sentences deliver the use case, storage destination, and visibility behavior with zero filler. The purpose is front-loaded in the first sentence, making it immediately scannable.

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?

Given the tool's complexity (6 params, no output schema), the description covers the essential workflow: what it creates, where it is stored, and its private nature. It does not state the return value, but for a simple creation tool this is a minor gap.

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 100%, so the schema fully documents all six parameters. The description adds no additional parameter-level detail beyond the schema, meeting the baseline but not exceeding it.

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 tool is for self-addressed captures (preference, decision, or note) with no recipient, and specifically says it writes a private seed packet to .notch/private/inbox/. This verb+resource+scope distinguishes it from siblings like create_packet, create_reply, and create_seed_packet, which involve sending or other packet types.

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?

Opens with 'Use for a self-addressed capture,' providing clear context for when to invoke this tool. However, it does not explicitly name alternatives or exclusion criteria, though the private/no-recipient framing implicitly contrasts with other create tools.

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