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

With no annotations, the description carries the behavioral burden and does add useful details: media is uploaded automatically, HTTP(S) URLs up to 500MB or base64 data URLs up to 75MB are accepted, and options are JSON-encoded. However, it does not disclose queue_id validation, whether the operation is reversible, or any error/response behavior, leaving transparency partial.

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 focused sentences with no filler. It front-loads the purpose, then packs the media constraints and options workflow into compact, easily parseable clauses.

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?

For a mutation tool with no output schema and no annotations, this is near-adequate: it covers purpose, media handling, and options. But it leaves the agent to infer what content accepts and how to obtain a valid queue_id, so it is not fully self-sufficient for correct invocation.

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 25%, so the description must compensate. It adds strong semantics for media_urls (URL forms, size limits, automatic upload) and options (JSON-encoded object from get_post_options). But content is never described, and queue_id is only implicitly tied to the 'custom publishing queue,' so compensation is incomplete.

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 starts with a specific verb and resource: 'Add content to a custom publishing queue.' The phrase 'custom publishing queue' clearly distinguishes this from direct-publish siblings like create_post or publish_post_now, so an agent can recognize its role immediately.

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 conveys a queue-based workflow and tells the agent to use get_post_options for valid options, which gives clear usage context. It does not explicitly contrast this tool with direct publishing alternatives, so it falls short of full when-to-use vs. when-not-to-use guidance.

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