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

Annotations already establish a safe, idempotent read, and the description adds real behavioral context beyond them: missing settings are omitted rather than defaulted, returned values are stored overrides and not computed styles, pagination terminates when next_offset is null, and mutation tools save immediately without staging. Those details materially change how an agent interprets and acts on the output.

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?

Front-loaded with the core capability and mode switch, then layered with operational caveats; each sentence carries information. Minor ambiguity around next_offset versus the schema's offset is the only wasted friction.

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 tool with no output schema, the description covers what is returned (full tree vs filtered widget inventory), how values should be interpreted (overrides, not computed styles), and pagination termination. It leaves the identity of post_id and the limit/offset mechanics to inference, which is the main remaining 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?

Schema coverage is only 17% (only site_id is documented), so the description must carry the load; it does explain the semantic pairing of widget_type with setting_keys and the efficiency intent of requesting only needed keys. But limit, offset, and post_id are never explained, and the description references 'next_offset', a name that does not appear in the input schema, which risks confusing offset handling.

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 ('Gets the full Elementor tree') and defines a second mode ('compact widget inventory when widget_type and setting_keys are supplied'), so the agent can pick the right shape of call. It does not, however, distinguish this tool from the close sibling wp_elementor_get_page_structure, which an agent may easily confuse with the tree mode.

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 concrete usage advice ('For batch inspection, request only the needed setting keys and follow next_offset until null') and an explicit exclusion ('Do not use filtered results for full-page replacement'). It omits guidance on when to choose this over wp_elementor_get_page_structure or wp_elementor_list_pages, so the alternative-selection story is incomplete.

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