hey_remove_from_collection

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

With no annotations, the description discloses idempotent behavior and return format ('{success, error?}'). It could be improved by mentioning permission requirements or that the operation is reversible via 'hey_add_to_collection'.

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?

Three efficient sentences: core purpose, key behavioral trait, and supplementary reference. No verbosity; every sentence serves a clear purpose.

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 no output schema, the description specifies the return format. Both required parameters are adequately described. The tool's simplicity and the provided context make this complete.

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% with good descriptions, but the description adds value by directing users to 'hey_list_collections' for obtaining collection IDs, aiding correct parameter usage.

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 'Remove an email thread from a collection' with a specific verb and resource. It distinguishes itself from the sibling 'hey_add_to_collection' by performing the inverse operation.

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 notes idempotency ('no error if not in the collection') and instructs to use 'hey_list_collections' to find IDs, providing clear guidance. However, it does not explicitly contrast with other removal tools like 'hey_remove_label', which could further aid selection.

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