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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so 'Read-only' is partly redundant. However, the description adds genuinely new context: the external .org directory source, the returned fields (slug, name, version, rating, requirements), and the fact that it executes without approval.

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?

Short and front-loaded with the action and data source. The read-only claim is restated twice ('Read-only' then 'its server marks it read-only'), which is minor waste but not harmful.

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?

Three parameters with full schema coverage and no output schema — listing the returned fields compensates well for the missing output contract. Only the guidance on picking this over sibling theme/plugin search tools is thin.

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 description coverage is 100% — search, site_id enum and the 1-50 per_page range are all documented in the schema. The description adds no parameter-level meaning beyond that, so baseline 3 applies.

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?

Specific verb and resource: 'Searches the wordpress.org theme directory by keyword.' Scoping to the .org directory implicitly separates it from installed-theme tools like emcp-tools-list-themes, but no sibling is named.

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?

Usage is only implied — an agent can infer this is for discovering candidate themes to install, not for inspecting the active theme. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. list-themes vs search-themes).

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