conversations_add_an_inbound_message

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

Annotations indicate readOnlyHint=false, so it is a write operation, but the description adds no behavioral detail beyond that. There is no mention of side effects (e.g., whether it creates a new message record, requires an existing conversation, or affects conversation state). The bur den falls entirely on the description, which is insufficient for a write operation with this complexity.

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 sentence and wastes no words, but it is under-specified for a tool with 17 parameters and nested objects. It is concise but not informative; the structure does not front-load key constraints or usage context. Adequacy is borderline.

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 the tool's complexity (17 params, nested objects, no output schema, no behavioral notes), the description is far too sparse. It fails to explain the purpose of an inbound message in the system, the required conditions (e.g., existing conversation), or how the payload should be composed. The agent must rely entirely on the schema, which is inadequate for 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 description coverage is 100%, so all 17 parameters have descriptions. The tool description adds no extra meaning about parameters (e.g., how the 'type' field interacts with other fields or which combinations are typical). Baseline of 3 is appropriate because the schema carries the load, but the description offers no additional insight.

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 states a clear verb ('Add') and resource ('an inbound message'), which distinguishes it from the outbound sibling tool. However, it is terse and does not clarify what constitutes an inbound message (e.g., SMS, email, call) or that it operates on an existing conversation. The name reinforces the intent, but the description adds little beyond the name.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it should be used to log incoming messages into an existing conversation, nor does it reference sibling tools like conversations_send_a_new_message or conversations_add_an_outbound_message. The agent must infer usage from the name and schema alone.

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