wordpress_plugin_exists

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

No annotations provided. The description doesn't disclose return format (boolean?), required input format, or behavioral traits like whether it checks by slug or name.

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?

Description is one short sentence, which is concise but lacks structure or additional details. It is front-loaded but too minimal for a helpful description.

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 low complexity (one param, no output schema), the description still omits crucial details like return type, parameter format, and edge cases, making it incomplete.

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?

Input schema has a single required parameter 'plugin' with no description. Schema description coverage is 0%. The description does not clarify what format the plugin identifier should take (e.g., slug, name).

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 checks if a plugin is installed, with a specific verb ('Check') and resource ('is installed'). It distinguishes itself from siblings like 'wordpress_get_plugins' and 'wordpress_get_plugin_status'.

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?

No guidance on when to use this tool versus alternatives like 'wordpress_get_plugins' or 'wordpress_get_plugin_status'. The description lacks context for selection.

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