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

Although annotations already declare read-only/idempotent/non-destructive, the description adds genuinely non-structured context: the manage_options capability requirement, the exclusions (scheduled posts not counted, private media not counted), and the multisite/connection scoping. These are exactly the kinds of caveats annotations cannot express.

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?

Front-loaded with the verb and resource, then a dense enumeration that is largely information-bearing. It is on the long side and the trailing AlphaBridge forwarding sentence is peripheral, but no sentence is filler.

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?

No output schema exists, and the description compensates by itemizing every returned metric group, including which statuses are excluded. An agent can predict the response shape and decide whether this tool answers its question without any further documentation.

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 zero parameters the baseline is 4, and the description confirms 'takes no arguments', removing any doubt about required inputs. There is no further parameter meaning to convey.

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?

States a specific verb+resource ('Get content counts of this site') and then enumerates exactly what is counted: per-post-type statuses, users total and per role, comment statuses, and media counts. This is clearly distinguishable from listing siblings like wp_list_posts or wp_list_users, which return entries rather than aggregates.

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?

Explicitly routes the agent to alternatives: 'The entries themselves are listed by wp_list_posts, wp_list_comments and wp_list_media.' It also gives scope rules (multisite: current site) and the precondition 'Needs manage_options', so an agent knows both when to use it and when not to.

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