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

Annotations already declare the mutation profile (readOnly=false, destructive=false, openWorld=true) and the title/description add the useful guarantee that only the caller's own settings are affected. However, the description says nothing about what happens to an existing link when none=true, nor why idempotency_key is offered when idempotentHint=false — a notable gap for a non-idempotent mutation.

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 short sentences, front-loaded with the three supported operations and followed by the scope constraint. It is essentially a verbatim restatement of the title, so it is slightly redundant but not padded.

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 five-parameter mutation with no output schema, the description covers the scope but omits the semantics of several combinations (how none versus slack_user_id interact, whether omitting both is a no-op, whether notices=false persists). It is adequate but leaves real ambiguity about safe invocation.

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 description coverage is 100%, so every parameter (none, notices, slack_user_id, idempotency_key) is already documented in the schema, establishing the baseline of 3. The description adds no parameter-level meaning beyond that.

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 concrete actions and a resource: choosing the caller's own Slack account, declaring they have none, or toggling notices about human tasks. 'Changes only the caller's settings' scopes it relative to teammates' links, though it never names a sibling tool to distinguish itself explicitly.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as summer_slack_member_links_match or summer_teammates_slack_link_create. The only routing hint (that slack_user_id comes from slack.member_link.read) lives in the schema, not the description.

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