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

With no annotations, the description carries the full behavioral burden but discloses almost nothing: it does not state that this is a mutating append, that idempotencyKey deduplicates retries, that a signature/publicKeyJwk may be required for auth, or what happens on parent-linkage. The only behavioral signal is the verb 'append'.

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 tight sentence with the action front-loaded and zero filler. It avoids bloat, though the extreme brevity is arguably part of the specification gap rather than a stylistic strength.

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 9-parameter, 5-required mutation tool with a nested object, no annotations, no output schema, and 0% schema description coverage, a single sentence is grossly insufficient. An agent cannot determine required fields, idempotency behavior, or authentication requirements from this definition.

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% across 9 parameters and 5 required fields, so the description must compensate and largely does not. It only hints at parentBeatId via 'parent-linked'; nothing explains agentLabel, clientInstanceId, idempotencyKey, signature, timestamp, or publicKeyJwk.

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 (Append/create) and a domain resource (a beat in the Wild Chronicle), which distinguishes it from the read/list siblings (wilds_list_chronicle, wilds_read_build). However, the term 'beat' and the parent-linking concept are domain jargon left undefined, so an agent that lacks context cannot fully pin down what object is being created.

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?

The description gives no when-to-use, when-not-to-use, or alternative-routing guidance. It does not explain how this differs from wilds_create_build or how/when to link a beat to a parent versus starting a new one, so the agent must infer usage entirely.

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