sf_get_contact

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

No annotations provided. Description implies read-only operation ('Retrieve'), which is accurate. However, lacks disclosure of any behavioral traits such as return format, pagination, or permissions. For a simple retrieval, this is adequate but not thorough.

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?

Single sentence, no waste, directly states purpose. Could be improved by front-loading the most critical info, but current structure is efficient and clear.

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?

Given simplicity (one param, no output schema), description is somewhat complete. However, does not explain what 'full record' entails, nor mentions any limits or common use cases. Context from sibling tools suggests it's part of a CRM suite, but the description alone is minimally adequate.

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?

Only one parameter (id) with schema description 'Salesforce Contact ID'. Description adds 'including Account name' but that refers to output, not parameter. Schema coverage is 100%, so baseline 3 applies; description provides no extra 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?

Description clearly states the tool retrieves a full Salesforce contact record including Account name. Verb 'Retrieve' and resource 'Salesforce contact record' are specific. Distinguishes from siblings like sf_get_account or sf_get_lead by focusing on 'contact', but does not explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives. Does not specify prerequisites, when not to use, or compare with similar tools like sf_search_contacts or sf_get_account.

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