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

Annotations already declare the write, idempotent, and destructive profile. The description adds useful scope: what is removed is the workspace context association, while the artifact itself remains undeleted. It does not contradict the destructiveHint annotation, which can refer to removing context rather than deleting the artifact.

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?

The description is a single, front-loaded sentence with no wasted language. The key behavioral constraint, that the artifact is not deleted, is stated directly.

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 simple unpin operation with rich annotations and an output schema, the description covers the essential action and non-deletion semantics. It could be slightly more complete by explicitly referencing workspace_pin as the inverse operation, but nothing critical for invocation is missing.

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 artifactId and the optional why parameter are already documented in the schema. The description adds no parameter-level details beyond what the schema provides, so the baseline of 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 states a specific verb and resource: remove markdown from a workspace's context. It also distinguishes the action from deletion by specifying that the artifact is not deleted, so an agent can tell this apart from artifact_delete.

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 implied by the action and by the contrast with deleting an artifact, but the description does not explicitly name workspace_pin as the inverse operation or state when to choose unpin versus deletion or leaving an artifact in place.

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