Liste Elementor Global Widgets

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

With no annotations provided, the description carries the full burden of disclosing behavior. It accurately describes a read-only listing action, but it does not explicitly state that it is non-destructive, nor does it mention any potential side effects, authentication requirements, or output characteristics. The description is honest but minimal, providing only the basic action without additional context.

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 in German that front-loads the verb and object. It contains no fluff, repeats nothing from the title unnecessarily, and every word contributes to the meaning. It is perfectly sized for the tool's simplicity.

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?

Given the tool has no parameters, no output schema, and a straightforward purpose, the description is sufficiently complete for an agent to understand what to expect. It clearly identifies the resource type (global/reusable widgets) and the action (list). It might benefit from noting that the output is an array or list of widget identifiers, but this is implied and not critical for such a simple tool.

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, so the schema is fully covered (100% coverage vacuously). According to the rubric, a baseline of 4 is appropriate when there are no parameters, and the description does not need to add anything about parameters. It is a simple list operation with no input requirements.

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 uses a specific verb ('Listet auf') and clearly specifies the resource ('alle globalen/wiederverwendbaren Elementor Widgets'), distinguishing it from sibling tools like elementor_list_widgets which likely lists non-global widgets. It is unambiguous and directly states what the tool does.

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 usage context is implied: use this tool when you need a list of global/reusable Elementor widgets. However, there is no explicit guidance on when not to use it or which alternative tools to consider (e.g., elementor_get_widget for details), so it only meets the 'implied usage' standard.

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