ghl_contact_get_by_business_id

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds OAuth scopes (contacts.readonly) and the pagination behavior (limit, skip, startAfter). This provides additional context beyond annotations.

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: it states the purpose, endpoint, OAuth scopes, and pagination instructions in a single paragraph with no redundant information.

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 no output schema, the description could mention the return format (e.g., array of contacts). It provides OAuth scopes and pagination guidance but omits response structure. The mention of 'full result sets' implies pagination behavior but not the shape of results.

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 coverage is 100%, so the description's role is reduced. It lists pagination params and adds usage context ('pass them to page through full result sets') but does not add new semantic meaning beyond the schema descriptions.

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 'Get Contacts By BusinessId' and the name reinforces it. It is specific (get contacts by a business ID) and distinguishable from siblings like ghl_contact_get_by_id (single contact) and ghl_contact_list (other filters).

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 mentions pagination params and advises to 'pass them to page through full result sets,' which provides some usage guidance. However, it does not explicitly state when to use this tool vs other contact retrieval tools (e.g., ghl_contact_get_by_id, ghl_contact_list) or specify prerequisites.

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