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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds genuinely useful behavior beyond them: the result is served from a cached saved list unless refresh is set, and canPublish=false means editorial review with content held unpublished until editor acceptance. That caching/staleness disclosure is the kind of trait annotations cannot express.

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 sentences, front-loaded with the scope and followed by the caching rule and output interpretation. Nothing is padding, though the second sentence is dense and partly restates the schema's refresh semantics.

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 an output schema present, return values need not be enumerated, yet the description still supplies the one interpretation that matters (canPublish meaning) plus the cache/refresh behavior. Combined with rich annotations and full schema coverage, an agent has everything needed to call and interpret this tool.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines refresh. The description's 'Uses the saved list unless refresh is true' paraphrases the schema rather than adding format or side-effect detail, so the baseline 3 applies.

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 names a specific verb (List) and resource (Medium publications) and scopes it precisely: publications with writer access or higher on the connected account. That resource is clearly distinct from siblings like list_linkedin_destinations or list_workspaces, so an agent can route without opening schemas.

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 gives a clear operational condition — 'Uses the saved list unless refresh is true' — and explains what the output means for the publish decision (canPublish true/false). It stops short of naming alternatives or when-not-to-use guidance, so it is strong context without explicit exclusion rules.

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