dm_chat_archive

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds specific behavioral details: it calls Bluesky's muteConvo and returns the chat with archived:true. This adds value beyond annotations.

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 extremely concise: two sentences with no wasted words. The primary action is front-loaded ('Archive (mute) a chat'), followed by platform and behavior details.

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 toggle operation with one parameter and no output schema, the description sufficiently covers the behavior. It could optionally mention the reversible nature via sibling, but not required.

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% and the description does not add any parameter-specific information beyond what the schema provides (chat_id is described as 'Chat hashid OR external_conversation_id' in both). Baseline of 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 clearly states the action ('Archive (mute) a chat'), the platform ('Bluesky only'), and the API call ('calls Bluesky's muteConvo'). It distinguishes from the sibling 'dm_chat_unarchive' by stating the operation and return value.

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 gives platform context ('Bluesky only') which helps when to use. It does not explicitly state when not to use or mention alternative tools, but the sibling 'dm_chat_unarchive' implies the opposite operation.

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