wordpress_upload_media_chunked_status

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

Despite no annotations, the description discloses session timeout (1 hour), returned fields, and error response (`{error_code: NOT_FOUND}`). It is transparent about the status query behavior, though it does not mention authentication or other side effects.

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 short paragraph, front-loaded with `[UNIFIED]`, and every sentence adds necessary information without redundancy.

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?

The description covers core behavior (resume after disconnect, session expiration, error case) and references sibling tools. Missing parameter descriptions are a minor gap, but overall it is complete for a status 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 coverage is 0%, but the description does not explain the `site` and `session_id` parameters beyond their mention. While `session_id` is inferable, the lack of explicit descriptions leaves a gap for the agent.

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 queries the state of a chunked-upload session, returning `received_bytes` and `next_chunk`. It distinguishes itself from sibling tools like `upload_media_chunked_start` and `upload_media_chunked_abort` by focusing on status querying.

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?

Explicitly tells when to use (to resume after a disconnect), mentions session expiry (1 hour), and advises to re-start with `upload_media_chunked_start` if expired or aborted. This provides clear context and alternatives.

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