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

Beyond the annotations (readOnly=false, destructive=false, openWorld=true) it discloses that the result is a private draft, that the original date is preserved, that a canonical link is attached, that no confirmation step occurs, the auth requirement (Cotlet API key with app access), and the failure mode. This is a rich behavioral picture for a mutation tool.

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 and generally tight, but the backdating and canonical-link behavior is stated twice ('copies a post from a URL into a draft, backdated, with a canonical link' then 'The draft keeps the original date and gets a canonical link to the source'), and the 'Medium: Medium's "Import a story"' prefix is redundant. Roughly a quarter of the text is repetition.

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?

Covers auth, privacy of the draft, mutation semantics, and the failure fallback, which is what an agent needs to call this safely. With no output schema, the description is silent on what the call returns (e.g. a draft identifier), a minor gap given a single required parameter.

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 only one parameter and schema coverage is 100%, so the schema already documents 'url' fully. The description's added constraint that the URL must be publicly readable is the only marginal value, which matches the baseline 3 when the schema does the heavy lifting.

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 ('copies a post from a URL into a draft') plus the distinguishing traits: backdating and an added canonical link. An agent can separate this from medium_create_draft or medium_update_story without inspecting either 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?

Gives an explicit failure condition and fallback: 'If Medium cannot read the page, the call fails and create_draft is the fallback.' That names the alternative and the condition that selects it, though it doesn't lay out when import is preferable to manually drafting from a URL in the first place.

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