missive_update_conversations

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

Discloses idempotency and non-destructive nature, consistent with annotations. Adds conditional requirement for 'organization' and explains the API method and behavior (no post/send). Does not contradict 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?

Concise yet informative, front-loaded with main purpose. Uses structured list of actions and clear parameter guidance. Minor redundancy (e.g., idempotent repeated) but no wasted sentences.

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 and only two parameters, the description covers essential context: operations, parameter structure, conditional requirements, and an API caveat. No gaps that would hinder correct invocation.

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%, but the description adds meaning beyond schema by explaining the one-object-per-id structure, the conditional need for organization, and the idempotent property. Helps agent construct correct requests.

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 'Updates conversation state' and enumerates specific actions (close/reopen, move, assign, etc.), distinguishing it from siblings like missive_create_post by explicitly saying it does NOT create a post or send anything.

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?

Provides clear context on when to use (update state without creating a post) and notes the absence of an archive action, suggesting alternatives. However, it does not explicitly exclude other tools or provide a comprehensive when-not list.

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