publer_upload_media_from_url

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

The description reveals a critical behavior: defaults to dry-run unless confirm is true and dryRun is false. This is helpful but lacks other behavioral traits like error handling, rate limits, or authentication needs, especially given no annotations are provided.

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 very concise at two sentences with no redundant information. It is front-loaded but the second sentence could be clearer. Still, it earns its place.

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 complex tool with many parameters and no output schema or annotations, the description is incomplete. It omits explanations for most parameters, return values, and success/failure conditions, leaving significant gaps.

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?

With 7 parameters and 0% schema description coverage, the description should compensate. It only explains the interaction of dryRun and confirm, leaving 5 parameters (url, title, altText, projectPath, workspaceId) unexplained. Insufficient for parameter understanding.

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 imports media from a URL, which is a specific verb+resource. It distinguishes from sibling tools like analytics or scheduling, though not explicitly excluding overlapping actions.

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?

No guidance is given on when to use this tool versus alternatives, such as when to schedule versus immediate upload. The description only mentions the dry-run behavior, providing limited usage context.

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