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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely new context beyond that: the deletion hits live data immediately with no build/publish step. It does not state whether the operation is reversible or whether confirmation (via the confirm-action sibling) is expected, leaving a modest gap.

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 short sentences, front-loaded with the activation trigger, then the behavioral nuance, then the disambiguation. No filler; the examples ('a booking or an old product') are concrete and earning their place.

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?

An output schema exists, so return values need not be described, and the three required parameters plus the live-vs-build distinction are covered. The only meaningful omission is whether the deletion is permanent/irreversible or requires a confirmation step, which an agent performing a destructive action would want to know.

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 67%: 'table' and 'row_ids' have descriptions that cross-reference list-site-data and get-site-data, while 'site_id' is undocumented. The description adds no format, count, or constraint detail for any parameter, so it neither compensates for the gap nor helps beyond the 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?

Specific verb (delete) plus resource (records/rows in a site's database table) with concrete examples (a booking, an old product). It also differentiates from the sibling edit-site by scope: record deletion vs. table/column removal.

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?

Opens with an explicit trigger ('Use this when the user wants to delete records...') and states the boundary case with the named alternative ('Use edit-site instead to remove a table or column'). Both when-to-use and when-not-to-use are covered.

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