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

Annotations already declare readOnly/idempotent/non-destructive; the description goes well beyond them by disclosing that pagination is absent, that broken themes (e.g. missing style.css) are silently omitted, the exact slug convention including collection namespacing, the active/parent-child semantics, the capability requirement, and that the call is forwarded by AlphaBridge Connect to a single site. These are non-obvious behaviors an agent could not infer.

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 core action and scope, then progressively adds return shape, exclusions, permissions, and forwarding. Dense and largely waste-free, though the single run-on sentence with semicolon-heavy clauses is harder to scan than a short structured list would be.

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?

With no output schema, the description fully specifies the return payload (slug, name, version, active with parent-child nuance), documents exclusions, the capability gate, and deployment context. An agent has everything needed to call and interpret the result.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The space is instead used to document the response shape, which is helpful but falls outside parameter semantics proper.

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 and resource ('List the installed themes') with scope ('all in one answer, no paging') and explicitly distinguishes itself from wp_list_theme_files, which handles files inside one theme. An agent can separate it from siblings without inspecting any schema.

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?

Clearly indicates when to use this (to enumerate installed themes) versus wp_list_theme_files (to inspect a single theme's contents), and names the required capability edit_theme_options. It doesn't discuss edge conditions like what to do if the list is empty, but the routing guidance is explicit.

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