wordpress_get_media

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

With no annotations provided, the description carries the full burden. It partially compensates by disclosing return content ('URLs, dimensions, and MIME type'), but omits safety characteristics (read-only status), rate limits, or error conditions.

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?

Two sentences with efficient structure. The '[UNIFIED]' prefix is unnecessary noise but does not significantly impede clarity. Information is front-loaded with the action verb.

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 lack of output schema, the description partially describes return values (metadata fields). However, with 0% parameter schema coverage and no annotations, it should explicitly document the two required parameters to be complete.

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% for both 'site' and 'media_id' parameters. The description fails to compensate by explaining what format 'site' expects (domain, URL, ID) or confirming that 'media_id' refers to the WordPress attachment ID.

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 ('media item'), and specifies the detail level ('detailed information', 'full metadata'). However, it does not explicitly differentiate from the sibling 'wordpress_list_media' (which retrieves multiple items) versus this single-item retrieval.

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 tool versus 'wordpress_list_media' or other media-related siblings. No mention of prerequisites like needing to obtain the media_id from a list operation first.

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