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

Beyond the annotations (non-read-only, non-destructive, open-world), the description discloses real behavior: typed teams lists undergo authorization before standalone creation, every version is stored in full and counts against the owner's storage, and the receipt is bounded but grants complete immutable content access. These are cost and auth facts an agent cannot infer from readOnlyHint/destructiveHint.

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?

Purpose is front-loaded and every clause carries a constraint rather than filler. The telegraphic compression ('homes it there', 'folder files it') makes it slower to parse than it needs to be for a 16-parameter tool, but nothing is wasted.

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?

With 16 params, an output schema and annotations already supplied, the description covers the decisions an agent must make: workspace vs. standalone, folder resolution, handoff, storage cost, and the table escape hatch. Return values need not be explained because an output schema exists.

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 75% and the schema already documents most fields, so the baseline would be 3; the description adds cross-field constraints the schema does not express (a workspace item takes no visibility, teams or publicAsset; no expected revision is needed; folder resolution order workspaceId → team → personal). It doesn't clarify alias, parentArtifactId or creatorContext, so it stops short of full coverage.

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 opening sentence gives a precise verb and resource ('Publish text as a versioned artifact') and the body scopes it further into workspace vs. standalone modes. It also explicitly routes a neighboring use case away ('data that grows by adding records belongs in a table'), letting an agent distinguish this from table_append_rows without opening any schema.

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 states the branch conditions clearly: workspace items need why and take no visibility/teams/publicAsset; standalone items can use those and are where typed teams lists are authorized. It names alternative paths explicitly (artifact_share_policy for later public readability, tables for growing data). What's missing is any guidance versus artifact_upload, artifact_patch or artifact_update.

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