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

With annotations already declaring readOnlyHint=false, destructiveHint=false, and openWorldHint=true, the description adds real context beyond them: no portal invitation or email is sent, the contact is linked to a company that may be auto-created, the action is reversible via a single SuiteDash edit, and an API key with app access is required. These are exactly the traits an agent needs before firing a silent write. It stops short of describing idempotency (duplicate contacts) or rate limits.

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 is front-loaded, but the no-invitation guarantee is repeated three times in slightly varied wording ('No portal invitation is sent', 'No portal invitation or email goes out'), and the 'so this tool runs without asking' aside is agent-directed filler rather than tool 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 create tool with full schema coverage and annotations, the description covers the important behavioral facts (silent creation, auto-company, reversibility, auth requirement). The one remaining gap is the return value/identifier of the created contact, which matters since there is no output schema, but nothing critical to invocation 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 description coverage is 100%, so role/email/name/company_name are already fully documented, including that the company is created if it does not exist. The description restates the company auto-creation rather than adding new semantics, so the baseline 3 applies.

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 ('Adds one contact to your CRM'), names the CRM classification (Lead/Prospect/Client), and notes the company-linking side effect. It never names or contrasts with a sibling such as suitedash_find_contact, so the agent gets a clear purpose but no differentiation within the SuiteDash toolset.

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?

The description implies when to use it (registering a new lead/prospect/client) and usefully signals that no invitation or email is dispatched, which separates it from invite-style flows. However, it names no alternative and gives no explicit when-not condition, so routing must be inferred.

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