wordpress_execute_shortcode

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. It only says 'process and execute,' which repeats the tool name without revealing potential side effects, return format, error behavior, or security implications of running arbitrary shortcode. The description adds no information beyond the name itself, making it dangerously opaque for a tool that executes code.

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 short sentence, which is concise, but it contains redundant wording: 'process and execute' are near-synonyms, so the first word adds no value. The front-loading is fine, but the phrasing could be more direct and information-dense. For a one-line description, it's not egregiously bloated, but it could be improved with more specific language.

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 minimal description for a tool with no annotations, no output schema, and one opaque parameter. A shortcode execution tool can have arbitrary side effects and output HTML, so the description should explain the required format, expected return value, and potential risks. None of this is present, making the description grossly incomplete for an agent to invoke it confidently.

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 a single required `content` parameter with no description, and schema description coverage is 0%. The description does not mention the parameter at all, offering no guidance on what `content` should contain (e.g., full shortcode string like `[gallery]`). The tool name hints that it's related to shortcodes, but the description fails to compensate for the schema's lack of detail.

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 the verb 'execute' and identifies the resource 'shortcode string', which clearly indicates the tool runs a shortcode. It distinguishes from sibling tools like wordpress_list_shortcodes and wordpress_shortcode_exists because execution is different from listing or checking existence. However, 'process' is vague filler that slightly reduces precision.

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 usage context, no mention of when to use this tool relative to alternatives, and no exclusions. It simply states what the tool does, leaving the agent to infer that it's for executing shortcodes. No alternative tools are referenced, such as wordpress_list_shortcodes for discovering available shortcodes.

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