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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety and idempotency are covered. Beyond that, the description adds only the pre-mutation workflow hint; it does not say what the schema contains, whether unknown widget_name errors, or whether results are cached. With annotations carrying the safety profile, a 3 is appropriate.

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?

Two short sentences, purpose first and the usage condition second, with no filler or repetition of schema fields. Every sentence 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 read-only lookup tool with rich annotations and no output schema, the description is adequate in shape but incomplete: it never explains what the returned schema is used for in practice or how an agent resolves widget_name. Adding a pointer to the widget-listing sibling would close the main gap.

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?

With 50% schema coverage, site_id is well documented in the schema itself (call list_sites first, no URL/post ID), and the description does not need to repeat that. The undocumented widget_name is only indirectly covered by "one widget type"; the description never says to obtain valid names from wp_elementor_list_widgets, which is the key missing semantic.

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?

"Gets Elementor control schema for one widget type" names a specific verb, resource, and scope. It is clearly distinct from siblings like wp_elementor_list_widgets or wp_elementor_get_page_data, though the term "control schema" is domain jargon that an unfamiliar agent may not fully parse.

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 second sentence gives an explicit trigger: use this before creating or updating unfamiliar widget settings. That is a clear when-to-use condition. It does not state when not to call it or name the mutation siblings directly, so it stops short of a 5.

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