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

Annotations only carry destructiveHint=true, so the description carries most of the burden; it does disclose real behavior beyond the schema (field-combination rules like firstName/lastName into name, and the link-shape rewrites for xUrl/linkedinUrl/primaryEmail/primaryPhone) plus 'all fields optional'. It does not mention auth requirements, duplicate handling, or what a successful create returns.

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?

Three compact clauses with no filler: purpose first, then the key optionality/mapping caveat, then the endpoint. Every sentence earns its place and nothing is buried.

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?

No output schema exists, so the description would ideally state what a successful create returns (e.g. the new record id) and how duplicates are treated; neither is covered. For a 10-parameter create tool with minimal annotations, the definition is adequate but leaves the agent guessing about the response contract.

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 the baseline is 3. The description adds a little value by restating the name-combination rule, but the per-field mapping details (xLink, linkedinLink, emails, phones) already live in the schema descriptions, so the description does not substantially extend parameter meaning.

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 ('Create a new person (contact)') and pins it to the underlying endpoint (POST /rest/people). The resource noun alone distinguishes it from the nineteen siblings (create_company, create_note, update_person, etc.) without ambiguity.

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?

Usage is implied by the create verb: it is clearly for creating, not updating or fetching. But there is no explicit guidance on when to use this versus twenty_update_person (e.g. upsert semantics) or how it relates to twenty_create_company for linked records, and no prerequisites are stated.

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