workflowmoves_wordpress_upload_media

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

Beyond the annotations, the description discloses genuinely useful traits: the call returns a retained background job rather than doing the work synchronously, it issues a new receipt, it requires operator-bound credentials, and its effects depend on permissions (write/network/publication plus conditional inference/download resolved via danceflow_component). It stops short of saying whether the upload is reversible or what happens on partial failure, but the async and auth context is real added value.

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?

At three sentences it is short and the follow-up job-polling instruction is placed early, which is good. However, phrasing such as 'canonical guarded transport', 'operator-bound credentials' and 'retained background job' is dense internal jargon that costs the reader more than the length suggests.

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?

An output schema exists, so return-value detail is rightly omitted, and the description covers the async job model and credential precondition. For a destructive, open-world write tool with a nested required arguments object, it still leaves the agent without a clear picture of what input it must assemble or what the operation will do to the site.

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 only 50%, so the description needs to compensate, and it does not: the nested 'arguments' object (manifest, receipt_out, expected_manifest_sha256) gets no explanation of what a manifest is, what the receipt is for, or why a manifest hash must be supplied. The only mapping offered is the write/network/publication effect flags, which the permissions schema already documents in its own description.

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 never states that this tool uploads media to WordPress; it says 'Invoke the canonical guarded WordPress transport,' which restates the namespace rather than naming the operation. The actual verb+resource only appears in the tool name, not in the text an agent reads, and no sibling (e.g. workflowmoves_wordpress_create_draft, workflowmoves_integrate_epk_media) is distinguished.

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 only actionable guidance is the follow-up 'poll danceflow_job_status', which is useful but concerns what to do after calling, not when to choose this tool. There is no statement of when to use it versus the other WordPress write siblings, no prerequisites beyond a vague mention of 'operator-bound credentials', and no exclusions.

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