wordpress_list_themes

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

No annotations provided, so the description carries full burden. It implies a read operation but doesn't explicitly state side-effect-free behavior, authentication needs, or rate limits. The phrase 'List installed WordPress themes' suggests read-only, but no confirmation.

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 very concise, no wasted words. However, the '[UNIFIED]' prefix is unusual but not detrimental. It could benefit from slightly more structure like separating core function from return details.

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 tool has two parameters and no output schema, the description is incomplete. It doesn't mention pagination, return format, or metadata contents. For a list tool with many siblings, more context is needed for correct selection.

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 coverage is 0%, and the description adds no detail about parameters. 'status' is not explained beyond default 'all', and 'site' is not described at all. The description fails to add meaning beyond the schema field names.

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 the tool lists installed WordPress themes and returns status and metadata. It distinguishes from 'wordpress_get_active_theme' (single theme) but doesn't differentiate from 'wordpress_wp_theme_list_detailed'.

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?

No guidance on when to use this tool versus alternatives like 'wordpress_get_active_theme' or 'wordpress_wp_theme_list_detailed'. The description is generic and lacks usage context.

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