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

Annotations already declare the mutation is non-readonly, non-idempotent, open-world, and non-destructive. The description adds important behavior beyond annotations: the invitation text is always empty, and daily/hourly limits, allowed hours, blacklist checks, random delays, and human approval are enforced.

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 usage guidance and then behavior, with no wasted clauses. The sentence 'Send a LinkedIn connection invitation' is mildly redundant after the opening sentence, but overall the structure is efficient and readable.

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 mutation tool with no output schema, the description covers when to use it, alternatives, invitation content, and enforced safeguards. However, despite zero required parameters in the schema, it does not explicitly state whether contact_id or linkedin_id and profile_id are practically required, leaving a small invocation risk.

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 all three parameters already have descriptions. The description adds a tactical preference not present in the schema: prefer contact_id because Salesbot resolves the LinkedIn identifier internally. That is useful beyond the structured fields, though it does not fully explain required parameter combinations.

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 states a specific verb and resource: 'Send a LinkedIn connection invitation.' It also clearly scopes the tool to a 'single one-off invitation outside campaigns,' distinguishing it from campaign-based siblings. An agent can identify the tool without opening the schema.

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?

It gives explicit when-to-use guidance for single invitations and names the alternatives for bulk sending: add_contacts_to_campaign and start_campaign. This routes the agent to the correct sibling for the many-recipient case.

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