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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotence, so the safety profile is covered. The description adds useful behavior — the title and preview are fetched from the page and the card lands in Unsorted — but says nothing about what happens on duplicate URLs or what is returned, so it adds moderate value only.

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?

A single compact sentence with the artifact and destination front-loaded and no wasted words. It is slightly terse to the point of being a fragment rather than a complete statement.

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?

There is no output schema, so the description could say what is returned (e.g. the created card or its ID) and how failures like an unreachable URL behave. With complete parameter docs and annotations carrying the safety profile, this is adequate but leaves real gaps for a create 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?

Schema coverage is 100%, with both url (http/https required) and board_id (from list_boards or board URL) documented in the schema. The description adds no parameter detail and its 'added to Unsorted' phrasing sits awkwardly against the required board_id, offering no clarification of that relationship.

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 the concrete artifact created (a link card with the page's title and preview) and its destination (Unsorted), which distinguishes it from add_note or add_column. It is a noun phrase rather than a verb-led statement, but the create action is unambiguous.

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 only implied: it is the tool for saving a web address as a card. There is no explicit when-to-use/when-not guidance and no mention of alternatives such as add_note for non-URL content or how this relates to upload_image.

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