wp_elementor_get_template_conditions

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

No annotations are provided, so the description carries the burden of disclosing behavior. The verb 'Get' implies a read-only operation, and the description clarifies what information is returned conceptually. However, it does not disclose output format, error behavior, or whether any side effects occur, which keeps it at an adequate rather than rich level.

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 with no filler. It front-loads the action and resource, then adds a helpful clarifying clause, earning 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?

This is a simple one-parameter getter with no output schema, and the description gives enough context for an agent to understand what it retrieves and why. It could elaborate on the exact shape of the returned conditions, but that is not necessary for correct invocation.

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 a single parameter already described as 'Template ID from wp_elementor_list_theme_templates'. The description does not add parameter-specific details, but with full schema coverage, the baseline of 3 is appropriate.

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 uses a specific verb ('Get') and names a precise resource ('display conditions for an Elementor Theme Builder template'). The clarifying clause 'which pages or post types it shows on' makes the tool's purpose easy to distinguish from the sibling wp_elementor_set_template_conditions.

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 makes it clear that this is a retrieval tool, and the sibling name wp_elementor_set_template_conditions provides an implicit contrast for when to use one versus the other. There is no explicit 'use this instead of...' routing or exclusion, but the context is clear enough for correct selection.

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