ghl_contact_get_by_id

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

The description adds the exact endpoint, version header, and OAuth scopes beyond the annotations' safety hints. It does not contradict annotations and provides meaningful behavioral context.

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 somewhat verbose including renaming history, but the endpoint and auth details earn their place. Could be more front-loaded but remains clear.

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?

Missing description of the return value (full contact object). Given no output schema, this omission reduces completeness. Otherwise covers endpoint, auth, and naming.

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 parameter contactId is fully covered by the input schema with example and description. The description adds no extra semantic detail beyond 'by ID', so baseline 3 applies.

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 it fetches a single contact by ID and explicitly distinguishes from sibling tools ghl_contact_list and ghl_contact_search_advanced by method and purpose.

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?

Explicitly contrasts with ghl_contact_list (deprecated list) and ghl_contact_search_advanced (filtered search), guiding the agent on when to use each alternative.

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