hey_add_to_collection

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

Discloses idempotent behavior and return format, which are key behavioral traits. No annotations are present, so description carries full burden; missing details on error cases or permissions, but sufficient for a simple mutation.

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 concise sentences front-loaded with purpose, idempotency, and return format. No wasted 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?

Covers key aspects (action, idempotency, return, parameter sourcing) for a simple add operation. Lacks explicit mention of preconditions (e.g., thread existence), but no output schema exists to compensate. Good overall.

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 covers both parameters fully (100% coverage). The description only reiterates the schema's guidance for collection_id and adds no new parameter-level meaning beyond idempotency (which is tool-level). Baseline score 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?

Clearly states the action ('add an email thread to a collection'), specifies idempotency, and mentions return format. Distinguishes from siblings like hey_remove_from_collection and hey_list_collections by providing context.

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 using hey_list_collections to find collection IDs, providing clear guidance. Does not explicitly state when not to use this tool versus alternatives, but the context is adequate.

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