ghl_conversation_add_inbound_message

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

The description indicates a mutation operation (adding a message) but does not disclose any behavioral traits beyond that. Annotations are minimal (non-destructive, non-idempotent), and no additional context is provided about side effects, prerequisites, or data handling. The direction field default in the schema may cause confusion.

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 concise with two key sentences plus endpoint and scopes. It is front-loaded with the primary purpose. Minor HTML formatting (<br />) is unnecessary but does not detract significantly.

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?

Despite the complex nested schema and no output schema, the description does not explain the return value, required conditions (e.g., existing conversation/contact), or how nested objects interact. It leaves the agent with insufficient context to use the tool effectively.

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?

Input schema has 100% description coverage, so each property is documented. The description adds no additional parameter meaning beyond what the schema provides, meeting the baseline expectation.

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 'Add an inbound message' and provides the endpoint and OAuth scopes. It identifies the specific resource (inbound message) and action (add), but does not explicitly distinguish from the sibling tool ghl_conversation_add_outbound_message, though the name implies the difference.

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 lacks guidance on when to use this tool versus alternatives like ghl_conversation_add_outbound_message or ghl_conversation_send_message. It only provides technical details (endpoint, scopes) without usage context.

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