Delete a form

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds 'Changes community state' and reiterates the confirm gate, but the confirm semantics are also captured in the schema, so net new behavioral disclosure is modest.

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?

Two short sentences, front-loaded with the action and followed by the key constraint. No filler or redundancy, though the phrasing could be slightly tighter.

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 simple delete tool with no output schema and annotations carrying the destructive/idempotency profile, the description covers the essential action and the confirm requirement. Nothing critical for correct invocation is missing, though a note on irreversibility would improve it.

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%, so account, confirm, and form_id are all documented in the schema itself, making the baseline 3 appropriate. The description only echoes the confirm parameter's requirement without adding syntax or format detail 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?

States a specific verb+resource ('Delete a form') that any agent can immediately map to a destructive operation. It does not distinguish itself from siblings like update_form or duplicate_form, but the verb 'delete' is unambiguous enough that differentiation is not strictly needed.

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 description adds a precondition ('requires confirm=true for the user-requested action'), which tells the agent how to proceed once it has decided to use the tool. However, it gives no when-not guidance or mention of alternatives (e.g., archive vs delete), leaving usage context only implied.

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