wordpress_get_active_theme

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

No annotations provided, so description carries full burden. While it lists returned fields (name, version, author), it fails to disclose read-only nature, authentication requirements, error cases (e.g., invalid site), or response format. 'Get' implies safe read, but this is not explicitly stated.

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?

Single sentence, front-loaded with action. '[UNIFIED]' prefix is metadata noise but doesn't significantly impede clarity. However, extreme brevity comes at the cost of omitting essential parameter documentation and behavioral context.

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 zero annotations, no output schema, and 0% parameter coverage, the description is insufficient. It hints at return value structure but leaves critical invocation requirements (the 'site' parameter) and behavioral safety profile completely undocumented.

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?

Critical gap: Schema has 0% description coverage for the 'site' parameter, and the description completely fails to compensate. No explanation of what 'site' represents (URL, ID, slug), its format, or where to obtain it. Agent cannot correctly invoke without guessing parameter semantics.

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?

Clear specific verb (Get) + resource (active WordPress theme information) + scope (name, version, author). Effectively distinguishes from sibling tools like wordpress_list_themes (all themes) and wordpress_wp_theme_update (modification) by specifying 'currently active'.

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?

Implied usage is clear—use when you need information about the currently active theme specifically. However, lacks explicit guidance on when to use this vs. wordpress_list_themes (which returns all themes) or wordpress_wp_theme_list_detailed. No prerequisites or conditions mentioned.

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