Initialize durable inbox

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

Annotations already declare readOnlyHint=false, and the description adds the concrete side effects: writing local configuration and registering the address. It explicitly states it does not create authenticated identity, which is valuable to prevent confusion with authentication tools. No contradiction with 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?

The description is two sentences: first gives the precondition, second states the action and a clarifying non-action. Every word earns its place, with no redundant information.

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?

The description conveys the core function, precondition, and an important exclusion (no identity creation). With an output schema present and annotations covering read-only/destructive hints, this suffices; it doesn't explore error cases or re-init behavior but is adequate for a simple init tool.

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 descriptions cover 100% of parameters, including that 'name' becomes the local: address and 'root' is an absolute path. The tool description adds no additional parameter-level semantics beyond mapping 'address' to the name parameter, so the baseline of 3 applies.

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 initializes a durable inbox by writing local configuration and registering the address for async cross-agent packet delivery. It uses a specific verb ('writes local configuration and registers') and identifies the resource, distinguishing it from packet creation and inbox read tools in the sibling list.

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?

Explicit precondition 'Use only after the user chooses an explicit local mailbox root and address' tells when it is appropriate to invoke. It does not name alternatives, but the context implies this is a setup step before other inbox operations; also clarifies it does not create identity to prevent misuse.

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