wordpress_get_plugins

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

With no annotations provided, the description carries full burden. It only states the purpose and does not disclose behavioral traits like output format, required permissions, or potential impacts. Essential information for safe invocation is missing.

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 phrase with no wasted words. It is appropriately sized for a simple parameterless tool, though it could be slightly more structured to form a complete sentence.

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 no output schema and no annotations, the description should explain what information is returned (e.g., plugin names, versions, statuses). The current phrase is too brief to be contextually complete for an agent that needs to interpret the results.

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 zero parameters, so schema coverage is 100%. Per guidelines, baseline is 4 for no parameters. The description does not add further parameter meaning, which is acceptable as there are none.

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 'Get all installed WordPress plugins', which identifies the verb (get) and resource (installed plugins). It distinguishes from siblings like wordpress_get_active_plugins by implying all plugins, but it could be more explicit about scope given the sibling wordpress_get_plugins_detailed.

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 is provided on when to use this tool versus alternatives such as wordpress_get_active_plugins or wordpress_get_plugins_detailed. The description does not mention exclusions or context, leaving the agent without decision-making help.

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