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

No annotations, so the description carries the burden — and it discloses the two traits that matter most: blast radius (changes apply to all campaigns and SDR processes using the account) and cost (no credits). It omits permissions/auth requirements and whether invalid field combinations (e.g. min > max delay) are rejected, keeping it short of a 5.

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?

Four tight sentences with no filler; the scope and blast radius are front-loaded before the alternative-tool pointer. Slightly dense but every clause adds 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?

For a 25-parameter, nested-object mutation with no annotations and no output schema, the description covers selection and blast radius but says nothing about the response, prerequisite reads (get_linkedin_account_settings), or validation/limit interplay. Adequate, with visible gaps for such a wide tool.

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 description coverage is only 8% across 25 parameters (only 'enabled' and 'calendly_url' are annotated), so the description must compensate. It does group several concepts (pitches, CTAs, signature, delays/limits) but leaves many params — timezone, contact_info, working_hours, agent_id, custom_instructions, tone/signature_mode enums — unexplained, so it partially but not fully closes the gap.

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 (change/update) and resource (settings of ONE LinkedIn account) and enumerates the domains it touches: AI auto-replies, invite/follow-up pitch, CTA, signature, reply delays/limits. The 'ONE LinkedIn account' scope plus the explicit pointer to update_campaign cleanly separates it from the campaign-level sibling.

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 the key usage rule ('Send only changed fields' = partial update) and an explicit alternative with its condition: use update_campaign settings.linkedinAutoReplyDisabled to disable AI replies for a single campaign. That is exactly the when/when-not guidance an agent needs.

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