unarchive_shared_step

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

The description states 'restore', which implies a state change, but provides no information about side effects, required permissions, error conditions (e.g., already active), or return value. With no annotations, more detail is needed.

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 sentence that conveys the core action without any unnecessary words. It is front-loaded and efficient.

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?

As a simple mutation tool with no output schema, the description omits important context such as what the tool returns, what happens if the step doesn't exist or is already active, and any prerequisites. More completeness is needed for reliable agent use.

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?

The only parameter 'id' is already fully described in the schema (must be a number). The description adds no further semantics, so it meets the baseline for 100% schema coverage.

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 uses the specific verb 'restore' and resource 'archived shared step', clearly indicating the action. It directly contrasts with the sibling tool 'archive_shared_step', making its purpose distinct.

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?

The description implies it is for reversing an archive operation, but does not explicitly state when or when not to use it, nor does it mention prerequisites like the shared step must be currently archived.

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