wordpress_get_media_analytics

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

No annotations are provided, so the description carries the full burden. It states 'Get media library storage usage statistics', implying a read-only operation, but doesn't disclose behavioral traits such as whether it requires admin permissions, if it's cached, what format the statistics are in (e.g., bytes, percentages), or if it includes historical data. This leaves significant gaps for an agent to understand how to invoke it effectively.

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 with no wasted words. It's front-loaded with the core action ('Get media library storage usage statistics'), making it easy to parse. Every word earns its place by conveying essential information without redundancy.

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 complexity of a tool that likely returns analytics data, the description is incomplete. No annotations exist to clarify behavior, and there's no output schema to describe the return values (e.g., total storage, used space, breakdown by media type). The description alone is insufficient for an agent to understand what to expect from the tool's output or how to interpret it.

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 input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description doesn't add parameter details, which is appropriate here. Baseline is 4 for 0 parameters, as there's nothing to compensate for, and the description doesn't introduce confusion.

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 verb 'Get' and the resource 'media library storage usage statistics', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'wordpress_get_media' (which likely retrieves media items) or 'wordpress_get_unused_media' (which identifies unused media), leaving some ambiguity about its unique scope.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'wordpress_get_media' and 'wordpress_get_unused_media', it's unclear if this tool is for analytics only, if it's complementary, or if it should be used in specific contexts (e.g., monitoring storage limits). No exclusions or prerequisites are mentioned.

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