Archive thread

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

No annotations are provided, so the description carries the burden. It discloses the primary action and locking behavior but omits permission requirements, effect on the thread, or error conditions. The locking detail adds some value beyond a simple verb.

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, clear sentence of 14 words. It is front-loaded with the key action and includes the optional locking detail without extraneous words.

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 tool with three parameters and no output schema, the description covers the primary purpose and the optional locking feature. The existence of 'unarchive_thread' as a sibling tool implies reversibility, which is partially addressed by the locking constraint. However, it could mention that archiving hides the thread from general view or require specific permissions.

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 100%, so the input schema already documents all parameters. The description adds the 'optionally locking' context, which maps to the 'lock' parameter, but does not add significant new meaning beyond what the schema provides.

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 clearly states the action 'Archive a thread' with a specific verb and resource. It also includes an optional locking behavior, distinguishing it from sibling tools like 'unarchive_thread'.

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 does not explicitly state when to use this tool versus alternatives. While the sibling 'unarchive_thread' implies a complementary pair, no guidance is given on scenarios for archiving vs. locking or prerequisites.

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