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

Beyond the annotations, the description discloses important behavioral traits: the link is one-time, expires in 15 minutes, is signed for exactly one content type, requires the pipelines:write scope, and spends no credits. It also previews the returned fields (uploadUrl, mediaUrl, Content-Type, curl command), which is valuable because there is no output schema.

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 dense but efficient, with every sentence earning its place: purpose, command-runner prerequisite, upload workflow, fallback behavior, permission requirement, and credit cost. The most important usage constraint is front-loaded in the first sentence.

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 tool with one parameter, no output schema, and a multi-step workflow, the description is complete: it explains what the tool returns, how to use those returned values, what prerequisites are needed, what happens if the agent cannot run commands, and the security/cost implications. An agent can decide whether and how to call this tool without ambiguity.

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 already documents the contentType parameter thoroughly with an enum and a description stating the PUT must send exactly this Content-Type. The tool description adds useful behavioral context by explaining that the link is signed for one content type and expires in 15 minutes, which helps the agent understand why choosing the correct contentType matters.

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 states a specific action and resource: creating a one-time upload link for putting a local file into the media library. It clearly distinguishes itself from import_media by describing create_upload_url as the prerequisite step that produces the mediaUrl to be used later.

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 gives explicit when-to-use guidance: only for a client that can run a command like Claude Code, Codex, or Cursor. It also provides a concrete alternative path (ask the person to drop the file into the Treza library and find it with list_assets) when the agent cannot run commands, plus the required next step of calling import_media.

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