wordpress_wp_theme_list_detailed

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

With no annotations, the description should disclose behavioral traits. It only states it lists themes, but does not mention that it is a read-only operation, potential authentication needs, or rate limits. The safety profile is not communicated beyond the obvious listing function.

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 a single, clear sentence. It is efficient and front-loaded with purpose. However, it could benefit from a brief note on the parameter to improve structure without adding significant length.

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 the single required parameter and lack of output schema or annotations, the description is incomplete. It does not explain the 'site' parameter, leaving critical ambiguity for the AI agent. The tool's behavior and required inputs are not fully clarified.

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 single parameter 'site' has 0% schema description coverage. The description does not explain what 'site' refers to (e.g., URL or domain). It adds no meaning beyond the parameter name, failing to compensate for the missing schema documentation.

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 lists all WordPress themes with detailed information including versions, status, and active theme identification. The name 'detailed' distinguishes it from sibling 'wordpress_list_themes' which likely provides a simpler list.

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 implies usage for obtaining detailed theme info but does not explicitly state when to use this tool versus 'wordpress_list_themes' or any exclusions. No guidance on prerequisites or context.

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