Create a form submission

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds a real behavioral detail beyond that: the operation mutates community state and is gated behind an explicit confirm=true flag tied to the user's request, which changes how an agent must behave before calling.

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 with no filler, and the state-mutation warning plus the confirm requirement are front-loaded. Every clause earns its 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?

For a 7-parameter, nested-object mutation tool with no output schema, the description is minimally adequate. It omits the mutually exclusive body options (payload vs payload_file vs individual flags) and what the tool returns, which the agent must reconstruct entirely from the schema.

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 86%, so parameter meaning is mostly carried by the schema, and the 3 baseline applies. The description only reinforces the 'confirm' semantics; it says nothing about the interplay between 'payload', 'payload_file' and 'elements' or the 'submission_on_behalf_of' behavior.

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 states a specific verb and resource ('Create a form submission'), which is unambiguous and clearly distinct from the read-oriented sibling 'get_form_submissions'. However, it is essentially a restatement of the tool name/title and adds no differentiating scope or detail about what kind of form or community is targeted.

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 gives one concrete precondition — confirm=true must be set for the user-requested action — which is genuine usage guidance. But it offers no when-not conditions, no exclusions, and does not point to 'get_form_submissions' or 'update_form' as alternatives, so the agent must infer the rest.

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