keap_get_contact

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

Since no annotations are provided, the description carries the burden. It uses the word 'Retrieve' and shows a GET endpoint, which implies a safe read operation, but it does not disclose behavior around missing contacts, authentication requirements, or rate limits. For a simple read tool this is minimal but perhaps adequate.

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 and includes only relevant details. The 'API:' and 'Args:' formatting is a bit unusual but still structured and front-loaded. It earns its place without verbosity.

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 the output schema exists (so return format is covered), the description sufficiently explains the action and parameters. It lacks error-handling notes or edge-case behavior, but for a straightforward GET-by-ID tool, this is close to 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 provides no descriptions (0% coverage), but the description fully compensates. It explains contact_id as the unique ID and optional_properties as a comma-separated list with an example, which is more informative than many 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 opens with 'Retrieve a single contact by ID,' which is a specific verb-resource pair that clearly distinguishes it from the sibling list tool (keap_list_contacts) and other resource-specific tools. The mention of 'single' explicitly differentiates from listing.

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 context is clear: it should be used when you have a specific contact ID and need that single contact's data. However, it does not explicitly mention alternatives or when not to use it, such as when you need multiple contacts and should use keap_list_contacts.

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