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

The annotations already mark this as destructive and not read-only, and the description adds useful operational context: deletion happens on live data immediately and without a build. It does not explicitly say the action is irreversible or whether confirmation is required, but the key behavioral trait beyond annotations is disclosed.

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 use case, followed by the immediate live-deletion behavior and the relevant alternative. There is no redundant or low-value text.

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?

Given the annotations, output schema, and sibling tools, the description provides enough context for an agent to select and invoke the tool correctly. It could be slightly more complete by mentioning irreversibility or confirmation expectations, but the essential routing and behavior are covered.

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%, with table and row_ids described in the schema, while site_id has no description. The description does not add parameter-level detail beyond schema, though its mention of database tables and records loosely supports the table/row_ids meaning. This is adequate but not compensating for the undocumented site_id.

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 description uses a specific verb and resource: deleting records from a WebTwizz site's database tables. It gives concrete examples (removing a booking or old product) and explicitly distinguishes the tool from edit-site, which handles table/column removal rather than row deletion.

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 exactly when to use the tool: when the user wants to delete records from a site database table. It also names the alternative for a related but different operation, saying to use edit-site instead to remove a table or column, which gives the agent a clear routing rule.

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