Delete Form

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value by saying the effect is removal from future selection and that system defaults are protected. It does not say whether the delete is reversible, what happens to forms already used in campaigns, or that a 'user_authorized' confirmation is demanded.

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, no filler, and the destructive scope constraint is front-loaded.

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?

Annotations cover the destructive profile and no output schema exists, which lowers the burden, but for a destructive mutation with two undocumented parameters the description still omits the confirmation requirement and the side effects on existing campaign usage.

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 0%, so the description must carry parameter meaning, and it does not. form_id is never explained, and the required confirmation field with its const 'user_authorized' is only obliquely echoed by 'explicitly approved'; an agent gets no explanation of that gate from either field.

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 ... workspace form') plus a scope qualifier ('from future selection'). That is enough to distinguish it from the CRUD siblings list_forms, get_form, create_form, and update_form, though none is named.

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?

'Explicitly approved workspace form' and 'system defaults remain protected' imply when deletion applies (workspace forms only, not system defaults), but the description offers no explicit when-to-use rule, no prerequisites, and no alternative such as a soft-disable path.

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