Contact Form 7 Formular aktualisieren

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely states 'updates' without revealing side effects, permission requirements, idempotency, overwrite behavior, or what happens when the formId is not found. This is a significant gap for a mutation tool.

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?

The description is a single sentence, but it is under-specified rather than concise. It repeats the tool name without adding value, failing to earn its place. A useful description would be longer or at least provide actionable details.

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?

This is a mutation tool with 6 parameters, no annotations, and no output schema. The one-sentence description is completely inadequate for understanding update semantics, field optionality, or return behavior. Even the update target (formId) is only mentioned in the schema, not the description.

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?

The input schema has 100% parameter description coverage, so the baseline is 3 even without additional info in the tool description. The description itself adds no parameter semantics, but the schema already explains each field (form, title, formId, mailBody, etc.) adequately.

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 'Aktualisiert ein CF7-Formular' is a tautology that simply restates the tool name and title. It provides no specific verb+resource distinction beyond the implicit 'update' action, and does not differentiate from sibling CF7 tools like cf7_list_forms or cf7_get_form.

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 gives no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or any scenario where cf7_update_form is preferred over other CF7 operations.

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