wordpress_advanced_wp_db_size

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

No annotations are provided, so the description carries full burden. It fails to disclose whether this is a read-only operation (implied but not stated), performance implications on large databases, or authentication requirements. Only states what data is retrieved, not behavioral characteristics.

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 with information front-loaded. Efficient structure with no wasted words, though the '[UNIFIED]' tag at the beginning is unexplained and slightly detracts from immediate comprehension.

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?

For a tool with only one parameter and no output schema, the description adequately covers the functional purpose but is incomplete regarding input requirements. The lack of parameter documentation is a significant gap given the low complexity of the tool.

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 0% and the description completely fails to document the 'site' parameter. It does not explain what constitutes a valid site identifier (URL, ID, slug), leaving the parameter entirely undocumented beyond its type.

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 resource (database size statistics) with specific details (total size, table sizes, row counts). It effectively distinguishes from siblings like wp_db_export or wp_db_query by focusing on size metrics. Deduction for the unexplained '[UNIFIED]' prefix which adds noise without value.

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 provided on when to use this versus related database tools like 'wordpress_advanced_wp_db_tables' or 'wordpress_wp_db_check'. No mention of prerequisites, permissions, or scenarios where this is preferred over alternatives.

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