crm_get_contact

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

Beyond the annotations (readOnly, idempotent, not destructive), the description adds crucial operational context: required OAuth scope, in-process cache with 300s TTL, write-invalidation behavior, audit log implications, and the not-found error for unknown/archived ids. No contradiction with 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 front-loaded with the core action, then adds usage guidance and operational details. Every sentence contributes essential information—retrieval, prerequisite usage, permissions, caching, invalidation, and error behavior—with no redundancy or fluff.

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 simple one-parameter schema, available output schema, and strong annotations, the description covers all necessary operational nuances: when to use, required scope, caching behavior, and error handling. The agent has complete guidance without needing to infer undefined behavior.

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 already fully describes the single parameter (contact_id) with its type and source ('as returned by search, list, or create'). The description's phrase 'by record id' adds no additional meaning beyond the schema, so a baseline 3 is appropriate.

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 the tool fetches one HubSpot contact by record id, specifying the returned fields (email, name, phone, company). It distinguishes itself from sibling tools like search, list, create, and delete by focusing on retrieval of a known id.

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 instructs to use the tool only after an id is known and names the alternative (crm_search_contacts) to find the id first. This provides clear sequencing and differentiates from the search tool.

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