Gravity Forms Formulare auflisten

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

No annotations are provided, so the description carries full behavioral burden. It transparently indicates a read-only listing operation ('Listet... auf'). However, it does not disclose output structure, pagination, ordering, or any limitations beyond the fact that it lists all forms. This is adequate but lacks depth.

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 that directly states the tool's purpose. There is no unnecessary verbiage, making it highly efficient and easy to parse.

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 list tool with no parameters and no output schema, the description covers the core functionality. It lacks detail about the exact response format (e.g., whether it returns IDs, titles, full objects), but the operation is so straightforward that the description is nearly sufficient. The absence of an output schema slightly reduces completeness.

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 and schema coverage is 100% (vacuously). With no parameters to document, the description does not need to compensate. The baseline for 0 parameters is 4, and the description appropriately focuses on the operation.

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 Gravity Forms Formulare auf' clearly states the action (listing) and the resource (all Gravity Forms forms). It distinguishes itself from siblings like gf_get_form and gf_get_entries by specifying 'alle' (all) forms, not a single form or entries.

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 provides no guidance on when to use this tool versus alternatives. For example, it does not mention that gf_get_form retrieves a specific form or that gf_get_entries lists entries. There is no explicit context, exclusions, or alternative suggestions.

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