Hole Elementor Global Fonts

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

With no annotations, the description must convey behavioral traits. It indicates a read-only retrieval and specifies the returned font categories, which is helpful. However, it does not disclose potential error conditions, return format, or dependency on the Elementor plugin being active, so transparency is partial.

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, focused sentence that front-loads the verb and resource, with a parenthetical list of the specific font types. It is concise, structured, and contains no fluff.

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 is very simple (no params, no output schema), and the description names the exact font categories returned. However, it omits contextual details like the return structure and prerequisites (e.g., Elementor must be active), leaving some edge cases unaddressed.

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?

This tool has zero parameters and an empty input schema, so the description doesn't need to add parameter details. The zero-parameter baseline is 4, and the description correctly ignores parameters, as there are none to describe.

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 clearly states the tool 'gets the global Elementor fonts' and lists the specific font roles (Primary, Secondary, Text, Accent). This distinguishes it from sibling tools like elementor_get_global_colors and elementor_get_global_settings, making the purpose unambiguous.

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 provides no guidance on when to use this tool versus other Elementor getters or list tools. It lacks any mention of prerequisites, scenarios, or alternatives, leaving the agent without decision support.

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