wordpress_shortcode_exists

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the action, not what happens when the shortcode is or isn't registered, return format, or whether any side effects occur. This is insufficient for a tool with no annotation support.

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 concise sentence that is front-loaded and contains no filler. Every word contributes to understanding and no unnecessary details are included.

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?

Although the tool is simple with one parameter, the description is incomplete for effective use. It does not disclose the return type (e.g., boolean), failure behavior, or any error handling. Since there is no output schema, the description should clarify what the agent can expect, but it does not.

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 schema only defines 'tag' as a string, and the description adds no further semantics. With 0% schema_description_coverage, the description should compensate by explaining what 'tag' means (e.g., the shortcode identifier), but it does not.

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 ('Check') and resource ('shortcode') with a clear condition ('is registered'). It clearly states the tool's purpose and distinguishes it from sibling tools like wordpress_list_shortcodes (which lists all) and wordpress_execute_shortcode (which runs one).

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 gives no explicit guidance on when to use this tool versus alternatives. It implies a simple existence check, but does not mention that one might use wordpress_list_shortcodes to enumerate or wordpress_execute_shortcode to run. No context or exclusions are provided.

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