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

Annotations already flag a destructive, non-read-only write; the description adds real context beyond that: prepare pairing, refusal behavior, preview mode, the fact that it cannot verify the owner was actually asked, and that doubt wording is saved verbatim. It stops short of saying what happens to prior standing content or whether the overwrite is recoverable, which matters for a destructiveHint 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?

The purpose is front-loaded and the length is moderate, with most sentences carrying operational information. However, the dense run-on phrasing and unexplained metaphors ('hand', 'finder marks', 'the owner's yes') make it harder to parse than necessary.

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 destructive, preparation-gated mutation with no output schema and low schema coverage, the description covers prerequisites, preview mode, and validation limits. It omits what the save returns, how standing_text is merged into existing standing content, and what happens to the prior version — gaps an agent would need before invoking confidently.

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 only 33%, so the description must carry the other two parameters. It does add meaning for owner_answer (stored in the standing's header; blank triggers preview) and standing_text (saved as written, with answer marks), but the explanations are embedded in opaque prose rather than clear field-level semantics.

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 first sentence gives a specific verb and resource — rewrites the home's current standing with the supplied text — and the prepare dependency distinguishes it from siblings. But key terms ('standing', 'a hand this home is missing', 'the finder marks') are metaphorical and undefined here, so an agent cannot fully picture what artifacts are produced or changed.

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?

It states a hard precondition (organize_prepare must have run recently on this connection, one prepare opens one save) and a clear alternate mode (blank owner_answer = preview that writes nothing). It does not name other siblings like save_note or supersede, but the when-to-use and when-refused guidance is explicit.

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