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

Annotations already mark this as destructive and non-read-only; the description adds exactly the needed context: one link per system, re-linking replaces the existing link, and `remove: true` clears it. It also explains the downstream lookup/sync benefit.

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?

Front-loaded and efficient: purpose, timing, replacement/removal behavior, and downstream usage are all covered without filler. Every sentence contributes useful operational context.

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 definition is largely complete for a destructive linking tool with no output schema, especially around replacement and removal semantics. The main omission is how `contact_id` identifies the person and what `profile_url` is for.

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 description adds meaning for `system`, `external_id`, `url`, and `remove`, and gives the `crm_id system:id` format used by get_contact. However, it does not explain `contact_id` or `profile_url`, which is a meaningful gap given only 50% schema description coverage.

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?

States a specific verb and resource: storing a CRM record id/url on a contact so later lookups skip the search. It also clarifies the relationship with get_contact by noting how the stored crm_id is consumed afterward.

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?

Gives clear timing guidance: use this after the person has been matched or created in HubSpot, Salesforce, Attio, or another CRM. It explains replace and remove behavior but does not explicitly state when not to use it or name alternative tools.

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