evolution_chat_archive

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

With no annotations, the description must disclose behavioral traits. It does not explain the implications of archiving (e.g., hiding from chat list, notification changes) or the need for the 'lastMessage' parameter. The behavior is oversimplified.

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 (four words) but lacks structure and detail. It under-specifies the tool, omitting necessary context for proper usage.

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?

Given the tool's complexity (4 parameters, nested required object, no output schema, no annotations), the description is insufficient. It fails to explain the return value or the purpose of 'lastMessage', making it incomplete for an agent to use correctly.

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 schema fully documents parameters. The description adds no extra meaning beyond 'archive true/false' and does not clarify the role of the complex 'lastMessage' object.

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 'Archive or unarchive a chat.' clearly indicates the tool toggles archive status on a chat. It uses a specific verb and resource, and is distinguishable from sibling tools like mark_read/mark_unread.

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?

No guidance on when to use this tool versus alternatives (e.g., mark_read). No prerequisites are stated, such as requiring the chat to exist or the user to have appropriate permissions.

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