wp_elementor_list_templates

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

No annotations are provided, so the description carries the burden. The verb 'List' reasonably implies a read-only operation, which is the main behavioral trait for a zero-parameter enumerator, but the description does not explicitly confirm no side effects or describe what the response contains. Adequate but not rich.

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?

A single front-loaded sentence with zero filler: the verb, resource, and scope appear first, and the parenthetical examples are the only addition. Every word 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 low-complexity tool with no parameters and no annotations, the description covers what the tool acts on and the scope. The only gap is the return format, which is not stated and cannot be inferred from an output schema because none exists — though a 'list' verb makes the collection return self-evident.

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 the rubric sets a baseline of 4 for that case. Nothing is left undocumented; the description's clarification of what counts as a template adds useful semantic color even with no parameters to explain.

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?

States a specific verb ('List'), resource ('saved Elementor templates'), and scope ('all'), with a parenthetical enumerating template kinds (sections, pages, headers, footers) that sharpens the resource. It is clearly distinct from siblings like wp_list_content, but it does not explicitly name or differentiate from any sibling, so it stops short of a 5.

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?

No guidance on when to use this tool versus alternatives. Nearby siblings such as wp_elementor_get_page, wp_elementor_widget_types, and wp_list_content overlap conceptually, and the description offers no selection criteria or exclusions.

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