wordpress_upload_media_chunked_start

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

With no annotations, the description discloses TTL (1h), hard cap (500 MB), and that it returns a session_id. It does not cover auth requirements, error conditions, or resource locking, but gives enough behavioral context for basic usage.

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 two concise sentences, front-loading the action and key outputs. Every word adds value 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?

Given no output schema, the description properly states the return value. It covers session lifecycle, TTL, and size cap. However, it omits details like error handling, required auth, and parameter roles, but the core functionally is 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?

The schema has 5 parameters with 0% description coverage, yet the description mentions none of them. It fails to add meaning beyond the schema, which is critical given the lack of schema descriptions.

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 action ('start a chunked upload session'), the resource ('large media file'), and the return value ('session_id'). It also mentions TTL and size cap, distinguishing it from other upload tools.

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?

It instructs to use the session_id for subsequent chunk/finish/abort calls and implies use for large files. While it doesn't explicitly state when not to use, the context of chunked upload and constraints (TTL, cap) provides clear guidance.

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