wordpress_advanced_system_disk_usage

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to indicate whether size calculations are performed in real-time (potentially slow) or cached, what units/format the data returns in (bytes, MB, JSON structure), or whether this is a read-only safe operation.

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 efficient sentence that front-loads the action. The only structural issue is the unexplained '[UNIFIED]' prefix which appears to be implementation cruft rather than useful semantic information.

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 single-parameter tool without output schema, the description adequately identifies what gets measured (the four component types). However, it misses the opportunity to describe the return format or whether results are cached, which would help the agent interpret results.

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?

With 0% schema description coverage, the description must compensate for the 'site' parameter but does not. It fails to specify whether 'site' expects a domain string, site ID, or slug, leaving the agent without guidance on parameter format.

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 'Get[s] disk usage statistics' (specific verb + resource) and enumerates the components measured: uploads, plugins, themes, and database. However, the '[UNIFIED]' prefix is unexplained noise, and it doesn't explicitly distinguish when to use this versus the sibling tool 'wordpress_advanced_wp_db_size' which appears to overlap for database sizing.

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 comprehensive disk usage tool versus more specific alternatives like 'wordpress_advanced_wp_db_size'. No prerequisites, permissions, or caching behavior mentioned.

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