wpscan_plugin_lookup

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Lookup a WordPress plugin', implying a read operation, but omits whether the call is read-only, has side effects, requires authentication, has rate limits, or what the response format is. This lack of detail hampers the agent's ability to manage expectations.

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 13-word sentence that is front-loaded with the verb and key details. Every word earns its place, making it efficient and easy for an agent to parse quickly.

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 simplicity (2 params, 1 required, no output schema), the description is passable. However, it does not specify what the lookup returns (e.g., vulnerabilities, metadata, or error cases), which is necessary given the lack of an output schema. It meets the minimum but is not comprehensive.

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?

With 0% schema description coverage, the description carries the full burden. It adds meaning by explaining that 'slug' is the plugin identifier and 'version' is optional, but it does not provide format, examples, or constraints beyond the schema's minLength. This is minimally sufficient but not rich.

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 verb 'Lookup', the resource 'WordPress plugin', and the lookup method 'by slug; optionally include a version'. It effectively differentiates from sibling tools like wpscan_theme_lookup by specifying the entity type.

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 its siblings (wpscan_core_lookup, wpscan_lookup_vuln, wpscan_theme_lookup). It does not mention any prerequisites, contextual triggers, or exclusion criteria, leaving the agent to infer usage solely from the tool name.

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