wp_elementor_get_shortcode_content

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

With no annotations, the description carries the full burden and only discloses unavailability and a reason about WordPress REST safety. It does not describe what happens when called or any actual retrieval behavior.

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 description is a single sentence with no redundancy and is easy to parse. However, it is concise because it omits the tool's purpose, so brevity is achieved through under-specification.

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?

The tool has one well-documented parameter and no output schema, but the description still fails to define the operation. The unavailability warning is useful context, yet an agent cannot tell what content would be retrieved or what response to expect.

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 100%, with page_id documented as an integer 'Page ID' and exclusiveMinimum 0, so the baseline of 3 applies. The description adds no parameter information, but none is required beyond 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?

The description does not state what the tool does. It only declares that the tool is experimental and currently unavailable, with no verb and resource. The tool's purpose must be inferred entirely from its name.

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 description tells the agent the tool is currently unavailable, which implicitly says not to call it. However, it provides no alternatives or conditions under which the tool should be used, so routing to sibling tools is not supported.

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