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

The description confirms the assignment action, which aligns with the destructiveHint annotation. It adds no additional behavioral details such as overwriting behavior or permissions beyond what annotations already provide.

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?

Two concise sentences, no fluff. The key constraint ('at least one is required') is front-loaded. Every sentence adds value.

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 mutation with 3 params and no output schema, the description covers the core functionality and the required parameter constraint. It could mention return behavior or errors, but it is generally 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?

The description adds the constraint that at least one of agent_id or team_id is required, which is not enforced by the input schema. With 100% schema coverage, this extra semantic information is helpful.

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 verb 'assign' with the resource 'conversation' and specifies the recipients (agent and/or team). It distinguishes this tool from siblings like groove_open_conversation or groove_close_conversation.

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 states that at least one of agent_id or team_id is required, providing a basic usage constraint. However, it does not explicitly discuss when to use this tool versus alternatives or mention prerequisites like existing agents/teams.

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