Archive or Restore Article

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

Annotations indicate non-read-only, non-destructive, and idempotent behavior. The description adds that archiving hides from normal views, is reversible via calling again with archived:false, and explicitly labels it as an update with reversible impact, going beyond annotation basics.

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 compact, front-loaded with the core action, and uses clear operation class/impact lines. Minor redundancy and the grammatical error 'a article' prevent a perfect score, but it remains efficient and well-structured.

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 two-parameter tool with strong annotations and full schema coverage, the description covers what the tool does, when to use it, its reversible nature, and its impact. No output schema is needed for this boolean toggle, and the description fully satisfies the context requirements.

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?

Both parameters are fully documented in the schema with clear descriptions for id and archived. The description reinforces the meaning of archived but does not add new information beyond the schema, so the baseline 3 is appropriate.

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 opens with 'Archive or unarchive a article', which names the exact verb and resource. It clearly explains that archiving hides without deleting and is reversible, distinguishing it from deletion and from sibling update/delete tools.

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?

Explicitly states this is the reversible alternative to deletion and should be preferred whenever the user wants something 'removed' without permanent deletion. This provides clear when-to-use guidance and implicitly contrasts with deletion.

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