handoff_inbox_reply

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

With no annotations, the description carries the behavioral burden and does well: it states that it appends a reply heading, marks the note answered, may push when the desk syncs through git, and skips duplicate identical replies. It omits error behavior for missing notes and any permission requirements.

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 compact and front-loaded: it opens with the action, then explains side effects, then defines `file`, then notes duplicate skipping. Every sentence contributes useful 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?

For a two-parameter mutation tool with no annotations or output schema, the description is fairly complete: it explains the main side effects, git push behavior, and duplicate handling. It could still say more about return values or failure modes, but the core operational context is present.

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 coverage is 0%, so the description must explain both parameters. It clarifies that `file` is the note's file name in the inbox folder, but `reply` is only implied by 'appends ... reply' and lacks any description of expected content or constraints.

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 gives a specific verb and resource: reply to an inbox note by appending a reply and marking it answered. It is clear what the tool does, though it does not explicitly differentiate itself from siblings like handoff_inbox or handoff_read.

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?

Usage is implied: use this to answer a note already in the inbox, with `file` naming that note. There is no explicit guidance on when to choose this over handoff_send, handoff_read, or how to first locate the note via handoff_inbox.

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