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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, yet the description still adds real substance: irreversibility, that no tombstone or epitaph record is produced, and the REST verb it wraps. It does not spell out permissions or return behavior, and it does not contradict the idempotent annotation.

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 endpoint and the action, then the consequences. The clipped 'No gravestone. No epitaph.' phrasing carries the no-residue semantic rather than being pure filler.

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, irreversible, output-schema-less operation, the description covers the essential agent concerns: what it does, that it is permanent, and that nothing is left behind. Minor gaps remain around authorization expectations and the fact that no identifier is actually marked required.

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% and both parameters (id as an alias for creature_id) are already documented in the schema, so the baseline of 3 applies. The description adds no argument-level detail, not even a hint that the identifier may be supplied under either key.

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 ('Surrender a creature') and names the underlying endpoint DELETE /api/house/release, so the mutation is unambiguous. The 'No gravestone' line implicitly distinguishes it from graveyard-related siblings like list_graveyard and resurrect_creature, though it never names an alternative outright.

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?

Conveys the operative condition ('it can't be undone'), which implies caution and that this is terminal rather than reversible, useful context next to resurrect_creature. It stops short of saying when to prefer this over other lifecycle actions or what prerequisites/auth are needed.

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