wordpress_execute_shortcode

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'process and execute' but doesn't clarify what execution entails—whether it's a read-only operation, if it modifies content, requires specific permissions, or has side effects (e.g., rendering output, triggering actions). The description is too brief to provide meaningful behavioral context beyond the basic action.

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 concise and front-loaded with a single sentence: 'Process and execute a shortcode string'. It wastes no words, but this brevity leads to under-specification rather than efficient communication. The structure is clear but lacks depth.

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?

Given the tool's complexity (executing shortcodes in WordPress can involve rendering, side effects), no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't address what the tool returns (e.g., rendered HTML, success status), error conditions, or dependencies. For a tool with potential behavioral nuances, this is inadequate.

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?

The input schema has 1 parameter with 0% description coverage, so the description must compensate. It mentions 'shortcode string' which hints at the 'content' parameter, but doesn't explain what constitutes a valid shortcode string (e.g., format, examples, or constraints). This adds minimal semantic value beyond the schema's type information.

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 states the tool's purpose as 'Process and execute a shortcode string', which is clear but vague. It specifies the verb ('process and execute') and resource ('shortcode string'), but doesn't differentiate from sibling tools like 'wordpress_list_shortcodes' or 'wordpress_shortcode_exists'. The purpose is understandable but lacks specificity about what execution entails.

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 alternatives. There are sibling tools like 'wordpress_list_shortcodes' (for listing) and 'wordpress_shortcode_exists' (for checking existence), but the description doesn't mention these or specify contexts for execution (e.g., in posts, pages, or widgets). Usage is implied but not explicitly stated.

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