elementor_lite_list_documents

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior: a hard cap on result count and the returned fields, and clarifies it does not export documents. However, 'at most ten' is in tension with the schema's configurable limit parameter, left unresolved.

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 no wasted words; the scope constraint and the returned fields both land immediately. It is compact without becoming a tautology.

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, the description helpfully names the returned fields (titles, ids, status), and annotations cover safety. Still missing for a two-param tool: what 'site' expects, whether the ten-item cap is overridable via limit, and any ordering or pagination behavior.

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?

Schema description coverage is 0%, so the description must carry the parameter burden and largely does not. 'At most ten' loosely hints at the limit default of 10, but the required 'site' parameter is never explained (format, identifier, where to obtain it).

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) and resource (Elementor documents) plus the exact fields returned (titles, ids, status) and a scope limit (no export). This distinguishes it from summarize_layout and ping_site, though it never names the siblings explicitly.

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?

There is no statement of when to choose this over elementor_lite_list_sites or elementor_lite_summarize_layout, nor any prerequisite about supplying a valid site. The only guidance is the negative scope note 'no document export', which excludes a capability rather than directing usage.

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