get_contact

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

No annotations are provided, so the description must disclose behavioral traits. The description only says 'Fetch', which implies a read operation but gives no details about error handling, return format, authentication requirements, or behavior when the contact is not found. This is a significant gap for a tool with zero annotation support.

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, front-loaded sentence with no filler. Every word contributes to understanding the tool's purpose.

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: one parameter, no output schema, no annotations. The description covers the core purpose and the parameter's type, but omits any detail about the return value or failure behavior. For such a simple tool, this might be acceptable, but it still leaves basic expectations (e.g., what happens if the contact doesn't exist) unstated, making it minimally 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 schema has no description for contactId (0% coverage), so the description must compensate. The description explains that the ID is a 'GoHighLevel contact id', which adds meaning beyond just 'contactId'. However, it doesn't specify format or any other nuances, so it is minimally sufficient for a single parameter.

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 a specific verb ('Fetch') and resource ('one contact') and clearly identifies the lookup by 'GoHighLevel contact id'. This distinguishes it from sibling tools like search_contacts (which searches) and create_contact (which creates). Purpose is immediately 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?

The description states this tool is for fetching a single contact by its ID, implying it should be used when the ID is known. It does not explicitly mention alternatives (e.g., 'use search_contacts if you don't have the ID'), but the context of having a specific ID is clear enough.

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