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

Annotations mark this as a non-read-only but non-destructive mutation; the description supplies the missing behavioral context — a password may be required for protected artifacts, invite links are single-account, and the side effect is membership visible in list_artifacts with an assigned role. It does not say what happens on repeat joins (idempotency) or what errors look like.

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?

One dense sentence, front-loaded with the primary action and the two identifier forms, with supplementary detail after semicolons. Every clause carries information, though the packed punctuation makes it slower to parse than split sentences would.

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?

No output schema, so the description correctly covers the observable result (artifact appears in list_artifacts with your role) and the auth nuances. Remaining gaps are edge behavior — already-a-member, wrong password, expired invite — rather than anything blocking a correct call.

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 0%, so the description carries the full burden and does: it defines id, url (share link or .../invite/<token>), and password as conditional ('with the password if protected'), and states the url/id either-or rule that the schema cannot express since zero params are required.

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 (join) and resource (artifact) plus all three access paths: share-link url, id, and invite token link. The outcome ('appears in list_artifacts with your role') makes it unmistakable versus sibling tools like get_artifact, create_artifact, or list_artifacts.

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 concrete selection rules: 'Provide either url or id' and the invite-link form is scoped 'for the invited account only', which is an explicit exclusion. It never states what to do if you already have access (e.g., prefer get_artifact), so the alternative-routing is implied rather than spelled out.

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