chat_getContact

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

No annotations are provided, and the description gives no behavioral details. It doesn't mention what happens in group chats, whether a missing contact returns null, or any auth or error conditions. The description's single sentence leaves all behavioral assumptions implicit.

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 extremely short, but this is under-specification rather than effective conciseness. It omits essential context that could be conveyed in one or two additional sentences, so the brevity is not a virtue here.

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?

With no annotations and no output schema, the description should explain what the tool returns, how it behaves in edge cases, and how it fits among the many sibling contact/chat tools. It does none of this, making the tool inadequately specified for reliable selection and 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?

The input schema has 100% coverage with descriptions for chatId and sessionId, so the structured data carries the parameter meaning. However, the description adds no additional explanation of how these parameters interact or are used to retrieve the contact, so it doesn't exceed the baseline.

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 '[Chat] Get the contact' states a getter action on a contact resource, but it is vague: it doesn't clarify which contact or how it relates to the chat. It does not distinguish itself from sibling tools like contact_getChat or client_getContactById, so the purpose is only broadly clear.

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?

There is no usage guidance at all. The description never indicates when to use this tool versus alternatives, nor any prerequisites or context, leaving an agent without direction for tool selection.

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