wp_performance_stats

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

With no annotations, the description must convey behavioral traits. It explains the aggregation behavior and per-site scoping, which is useful. But it omits side effects, authentication needs, or whether the operation is read-only. The description provides moderate but incomplete transparency.

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 two sentences, concise and front-loaded with the purpose. Every sentence adds meaningful context without unnecessary words.

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, the description should help the agent understand return structure. It mentions top-level metrics and siteSpecific section but doesn't specify metric names or formats. It's adequate but leaves gaps for an agent to fully understand the response.

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?

Schema descriptions cover 100% of parameters. The description adds value by explaining that the site parameter triggers per-site stats in a siteSpecific section, which goes beyond the schema. For category and format, it adds no new meaning, so baseline 3 is appropriate.

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 it retrieves real-time performance statistics and metrics, mentioning top-level aggregates and per-site stats. It doesn't explicitly differentiate from sibling tools like wp_performance_history or wp_performance_alerts, but the purpose is sufficiently clear.

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 explains that top-level metrics are session-wide and per-site stats appear with a site parameter, giving some context on when to use the site parameter. However, it lacks guidance on when to choose this tool over alternatives (e.g., benchmark vs. stats) or when not to use it.

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