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

Adds substantial context beyond annotations: it explicitly states the call writes nothing to the CRM and does not modify existing records, only governs future owner assignment. It also discloses the validation/refusal behavior (refused, naming each problem, until the rules can route every record) and the HubSpot platform constraint.

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?

Purpose and default state are front-loaded, and nearly every sentence carries new information (refusal conditions, HubSpot exception, no-write clarification). It is a dense single block with nested parentheticals, which slightly hurts scanability for an agent.

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?

For a two-parameter, no-output-schema tool, the description covers prerequisites (call list_crm_connections first), the full meaning of both modes, failure modes, and the platform-specific exception. Nothing needed to invoke it correctly is missing.

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 baseline is 3, but the description goes further by explaining what each enum value actually means operationally (org's own assignment rules vs. LiveCRM deciding via connection Assignment rules, accounts first, contacts inheriting account owner). That is additive over the bare enum list.

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: setting who decides the owner of records LiveCRM creates on a given connection. It is clearly distinguishable from siblings like set_assignment_config and set_contact_owner_inheritance, and the two enum values are defined in plain language.

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 strong when-to-use context: the default ('crm' is how every connection starts), the conditions under which 'livecrm' is refused (no active routing field, no active pool, no eligible rep), and the HubSpot exception where 'crm' is refused. It points to list_crm_connections for reading the current mode, but never names an alternative tool for changing owner-related configuration.

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