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

With no annotations, the description carries the full burden and does well: it discloses the 24-hour TTL behaviour (first reply sets it, later replies reset it) and two important security caveats – untrusted bridge text (prompt injection guard) and unverified speaker labels. It stops short of explaining permissions, error behaviour, or whether 'resolve' closes the meld.

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?

Four short sentences, front-loaded with the core action and then the TTL and security caveats. Dense with little waste, though the two TTL sentences could be merged without loss.

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 mutation tool with no annotations and no output schema, the description covers TTL semantics and injection safety but omits what a successful reply returns, whether it creates or resolves state, and any permission requirements. Adequate but leaves real gaps for a write operation.

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 all three parameters (pin, code, context) are already documented in the schema. The description adds nothing param-specific, 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 uses a concrete verb+resource ('Append a reply on the same bridge'), which is clear enough for an agent to act on. The one weakness is the mismatch with the tool name 'meld_resolve', which suggests closing/resolving rather than replying, and the description doesn't reconcile this or name meld_create/meld_read as alternatives.

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 by 'Append a reply on the same bridge' – the reader infers this is for replying to an existing meld rather than creating one. However, it never states when to use this over meld_create or meld_read, nor are there explicit exclusions or prerequisites.

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