MCP Hub

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

With no annotations provided, the description carries the full burden but only discloses basic mechanics. It mentions the 'public URL' requirement but fails to address idempotency, return values (media ID, attachment data), supported file types, size limits, error handling, or authentication needs for the WordPress site.

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 appropriately brief with two sentences that front-load the action. However, the '[UNIFIED]' prefix appears to be implementation metadata rather than descriptive content, slightly cluttering the definition without adding value to the agent.

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 0% schema coverage, no annotations, and no output schema, the description is insufficient for a 5-parameter media upload tool. It omits the metadata parameters entirely, provides no information about the return structure (crucial for obtaining the uploaded media ID), and lacks safety/constraint details expected for file operations.

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 coverage is 0%, requiring the description to compensate. While 'url' is implied by 'Downloads file from public URL' and 'site' by 'uploads to WordPress', the three metadata parameters (title, alt_text, caption) are completely undocumented. The description makes no mention of these optional media attributes despite their importance for accessibility and organization.

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 downloads from a public URL and uploads to the WordPress media library, using specific verbs ('Upload', 'Downloads') and resources ('media', 'file'). It distinguishes from siblings like directus_import_file_url by specifying 'WordPress' and uses the technical term 'sideload' to clarify the mechanism.

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 implies usage by explaining the mechanism (URL to WordPress), but lacks explicit when-to-use guidance, prerequisites beyond the public URL requirement, or alternatives. It doesn't clarify when to use this versus hypothetical local file upload or direct media creation tools.

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