create_dm

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

The description states the tool can either open an existing DM or create a new one, which is a key behavioral trait. However, it does not disclose potential side effects (like creating a space), required permissions, rate limits, or what the return value signifies. Since no annotations are provided, the description should cover more behavioral aspects.

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 a single, concise sentence that clearly states the action and the required parameter. There is no extraneous information.

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?

The tool is simple with one parameter, but the description does not explain the return value or the next steps after creating/opening a DM. For an agent to use this tool effectively, it might need to know if the DM is immediately ready for sending messages. The output schema is missing, so the description could include what is returned.

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 input schema already provides a description for the 'email' parameter ('Google email of the user'), and the description merely restates this. With 100% schema coverage, the description adds no additional semantic value beyond what is already in the schema.

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 uses the verbs 'Open or create' with the resource 'DM conversation', clearly distinguishing this tool from siblings like 'send_message' which sends to an existing conversation, and 'list_spaces' which lists existing conversations.

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 does not provide any guidance on when to use this tool versus alternatives such as 'list_spaces' to find an existing DM or 'send_message' to directly send a message. No exclusion criteria or prerequisites are mentioned.

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