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

Annotations already declare non-read-only, non-destructive, non-idempotent, open-world. The description adds substantive behavior: full version storage contributing to owner storage quota, no expected-revision requirement, and bounded content access on return. That is real context beyond the annotations, though the 'bounded content access' phrasing is vague.

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?

Front-loaded with the core action, but the middle sentences are dense run-ons with nested parentheticals ('folder files it: a folder id, or a slug (in workspaceId, else in team, else your personal folders)') that slow comprehension. Information density is high but readability suffers.

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 13-parameter tool with an output schema, the description covers the critical decision points (workspace vs standalone, folder resolution, storage implications). Unmentioned params like creatorContext, inputReferences, and parentArtifactId are documented in the schema, so the gap is minor.

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 69%, so the schema already documents most parameters including `why`, `folder`, `teams`, and `audience`. The description reinforces the `folder` slug-resolution order and the workspace-item constraint on `why`/`teams`, but mostly restates what the schema descriptions say. Average-value addition only.

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?

States a specific verb and resource ('Upload a strictly encoded base64 file') immediately, and clarifies the workspace-item versus standalone distinction. It does not name sibling tools directly, but the closing contrast with tables gives partial differentiation.

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?

Gives conditional routing: workspace items need `why` and take no `teams`, standalone creation requires typed team authorization, and record-growing data belongs in a table instead. The alternatives are implied rather than named (no mention of artifact_bulk or bundle tools), but the when-to-use conditions are explicit.

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