archive_shared_step

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

Describes outcome (archived steps readable but hidden from active library). No annotations provided, so description carries burden; lacks mention of permissions or side effects but covers core behavior.

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 concise sentences: first defines action and outcome, second gives usage guideline. No redundant information.

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 archive operation with one parameter and no output schema, the description fully covers purpose, behavior, and a critical usage check via sibling tool.

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?

Single parameter 'id' with schema coverage 100%. Description does not add extra meaning beyond schema's own description of the parameter.

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?

Clearly states action (archive), resource (shared step), and effect (retire from active use, remain readable but hidden). Distinguishes from sibling tools like unarchive_shared_step.

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 advises to run 'get_shared_step_usage' first to check impact, providing when-to-use and precondition guidance.

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