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

Annotations already declare destructiveHint=true, readOnlyHint=false, so safety profile is known. The description adds the SuperAdmin permission requirement and the delete toggle, which is useful extra context, but omits irreversibility details or response behavior.

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?

One compact sentence front-loads the action, enum options, delete flag, permission level, and UI mapping with zero 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 5-param mutation tool with no output schema, the description covers purpose, permission, and the delete path reasonably, but leaves confirm and id semantics undocumented.

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 20%, but the enum values are fully listed in the schema. The description clarifies that status accepts those four values and that delete:true deletes, yet the 'confirm' boolean and entryId/farmId semantics remain unexplained in both description and schema.

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 specific verb and resource ('Update a waitlist prospect status') and names the exact enum values, distinguishing it from list_rentahatch_waitlist. However it does not explicitly name siblings to differentiate, relying on context.

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 mention of 'SuperAdmin only' and 'Mirrors Admin > Waitlist' gives some context, but there is no explicit when-to-use vs alternatives or when-not guidance beyond the obvious update task.

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