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

Annotations already declare non-readOnly, idempotent, non-destructive, and closed-world, so the bar is lower; the description still adds real value by disclosing that webhook mode performs a POST to the supplied http(s) URL and that the change is scoped to the caller and permitted while pending. It does not describe failure behavior for an invalid or unreachable target.

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?

Three tight sentences, front-loaded with the action and the mode semantics before the scoping notes. Nothing is redundant; even the parentheticals carry parameter meaning.

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 two-parameter setter with no output schema, the description covers semantics, scope, and availability. The only gap is what the call returns or how to verify the new setting took effect, which the agent must infer.

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 coverage is only 50% (notify_method has no description), yet the description compensates fully: it maps each enum value to the expected notify_target form ('POST to notify_target, an http(s) URL' vs 'an address' vs 'none'). This adds meaning beyond the schema's bare enum and the partial target description.

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 ('Change how GetBody pings YOU') and immediately enumerates the three notify_method modes with their target semantics. No sibling tool touches notification settings, so the agent can identify this unambiguously.

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?

Explains the situations that produce notifications (operator decisions on listings and lease requests, lease inquiries and host responses) and two important preconditions: it works while the agent is still pending, and it only affects the caller's own agent. It does not name a when-not condition, but there is no competing sibling to route away from.

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