wp_discover_site

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

With no annotations, the description carries the full burden. It discloses that the tool persists a profile and explains the two transport modes. It does not cover error cases or permissions, but for a discovery tool the key behaviors are stated.

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?

Two tight paragraphs: the first states purpose and method, the second adds the prerequisite context and parameter explanation. No fluff, key information is front-loaded.

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?

Covers purpose, operational method, and its role as a prerequisite. It doesn't specify return values, but there is no output schema and the tool's purpose is clear. Slightly more detail on what the profile looks like would help, but it's not essential for invocation.

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 has zero description coverage, but the description explicitly defines `install` as 'the WP Engine install name', providing essential meaning beyond the bare string type. It lacks format examples, but this is sufficient.

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 'fingerprint' and the resource 'install', enumerating exactly what is captured (active theme, builder + Divi version, WP/PHP versions, plugin count, multisite). It also distinguishes itself from siblings by being the 'learning entrypoint' that other content/settings tools depend on.

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?

It explicitly positions the tool as the prerequisite: 'This is the learning entrypoint: content/settings tools expect a profile to exist.' It also describes the transport-aware behavior (REST vs SSH/WP-CLI), giving clear context for when it is appropriate.

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