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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive write; the bar is therefore lower. The description adds the gallery-upload exclusion, but says nothing about idempotency behavior (despite the required idempotencyKey), publishing visibility, or what happens on republish.

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?

Two tight sentences, zero filler, with the core action front-loaded and the constraint following. It is appropriately sized for the amount of information conveyed.

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 7-required-parameter write tool with no output schema and only thin annotations, the description covers purpose but leaves important gaps: the role of idempotencyKey, what humanInvolvement/initiated are meant to capture, and what a successful publish produces. Adequate but not complete.

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 71%, so the schema already documents most fields including enums for medium and initiated. The description only loosely gestures at the params ('creator note and method details'), adding little syntax or meaning beyond what the schema provides, matching the baseline for high-coverage schemas.

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 gives a specific verb+resource (publish a work hosted elsewhere) and explicitly scopes out gallery uploads, which is a meaningful boundary. It does not, however, name or contrast against any sibling tool, so the differentiation is bounded by the negative constraint rather than explicit routing.

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?

Usage is implied by the nature of the tool and reinforced by the 'does not accept gallery uploads' exclusion, which functions as a when-not hint. There is no explicit statement of when to choose this over a sibling like morrowkin_update_work_request, nor any prerequisites.

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