Contact Form 7 Formulare auflisten

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

No annotations are provided, so the description carries the full burden. However, it merely restates the title without adding behavioral context such as return format, pagination, or any side effects. The tool is a simple read-only list operation, but the description offers no additional insight into what the output contains or any edge cases.

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 concise sentence with no unnecessary words. It is effectively one line that communicates the core purpose, though it is so brief it borders on being a tautology. Still, it is appropriately sized for a simple listing tool.

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?

With no output schema, no annotations, and no behavioral details, the description fails to convey what the tool actually returns (e.g., form IDs, titles). For a tool with zero parameters and no structured output, the description should at least mention the kind of data returned, making the context incomplete.

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 tool has zero parameters, which earns a baseline score of 4. The description adds no parameter details, but none are needed since the schema is empty and the operation requires no inputs.

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 'Listet alle Contact Form 7 Formulare auf' clearly states the action (list), the resource (Contact Form 7 forms), and the scope (all). It distinguishes itself from sibling tools like gf_list_forms and cf7_get_form by explicitly naming the plugin and the list-all behavior.

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 implies usage for retrieving a list of all CF7 forms, but it does not explicitly state when to use this over alternatives. There is no mention of singular-form retrieval via cf7_get_form or that other plugins have their own list tools, leaving usage to be inferred rather than clearly guided.

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