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

With no annotations, the description carries the full burden; it does disclose that the line is signed and appended to a ledger and that a ledger event id is returned. However, it never states that the ledger is append-only/immutable, what signing credentials or permissions are required, or whether a failed write is retryable — key traits for an audit-mutation tool.

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?

A single compact sentence with the action front-loaded, the enumerated kinds in a parenthetical, and the return value at the end — no wasted words. The trailing clause 'for a reference id from this door' is slightly ambiguous phrasing, but the structure remains efficient.

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?

An output schema exists, so explaining the return value is optional and the description's mention of the ledger event id is a bonus. What is missing for a three-parameter write tool with no annotations is the meaning of the optional note field and any signing/permission preconditions or immutability guarantees.

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% and the schema declares kind as a bare string with no enum, so the description's enumeration of kinds (read · claim · order_intent · note) is essential information the schema lacks. It also clarifies reference_id as coming 'from this door'. The optional note parameter receives no explanation, which holds it below a 5.

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?

States a specific verb and resource: 'Write a signed audit line to the ledger', and enumerates the permitted kinds (read, claim, order_intent, note). This is clearly distinguishable from siblings like claim_row or create_order_intent, though the phrase 'for a reference id from this door' is cryptic and no sibling is named explicitly.

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 only implied: an agent can infer it should call this to record an audit entry of a given kind, and the kind list hints at which situations map to which value. There is no explicit when-to-use, when-not-to-use, or guidance on whether logging is mandatory before/after other operations such as claim_row.

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