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

Annotations already declare readOnly/idempotent/non-destructive, so 'read-only, runs straight away' adds nothing. However, the description does disclose the concrete return shape (id, name, type, date_modified) which is genuine behavioral value given there is no output schema. Unaddressed: result ordering and how limit truncation is reported.

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 purpose and return fields are front-loaded, which is good. But the bracketed native-MCP aside, the '(site: demo.royalplugins.com)' note that duplicates the site_id schema description, and the annotation-repeating 'read-only, runs straight away' all consume space without adding decision-relevant information.

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 zero-required-param read tool with full schema coverage and no output schema, the description covers purpose, filters, return fields, and the downstream workflow step. Remaining gaps are minor: no indication of sort order or whether templates can be found by name/keyword.

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 100%, so all three parameters (type enum, limit default, site_id) are already documented. The description only restates 'filter by type if needed' and never discusses limit or site scoping, so it does not meaningfully exceed the schema.

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 and resource: 'Enumerate saved templates from the Elementor Library (the elementor_library custom post type).' It also names the returned fields (id, name, type, date_modified), so an agent can distinguish it from listing plugin/theme templates or from the native Elementor structure tools it explicitly cross-references.

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?

Gives explicit sequencing: 'Use this before elementor_import_template to discover available templates,' and notes optional type filtering. It also points at native-MCP alternatives (elementor/build-composition, elementor/get-page-structure) but does not say which to prefer or when, so routing still requires some inference.

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