crm_lookup_contact

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

No annotations are provided, so the description must carry full behavioral disclosure. It states the tool is read-only and describes the returned data categories, which is helpful. However, it omits potential error conditions, permission requirements, and any data freshness caveats, making it only partially transparent.

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 short and front-loaded with the purpose. The return information is captured in a compact bullet-like list, and the Args section is clearly structured. No wasted words.

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 the tool's simplicity (one parameter, read-only, output schema exists), the description covers the essential aspects: purpose, parameter format, and return categories. It lacks explicit error handling or use-case differentiation, but those are less critical for a focused lookup 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?

The schema provides only a parameter name and type with no description. The description compensates fully by explaining the 'handle' parameter in the Args section, including the useful detail that it can be used with or without '@'.

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 clearly states the verb ('Get'), the resource ('stored fact sheet'), and the target ('one local CRM contact by handle'). It distinguishes from sibling tools like lookup_lead by explicitly scoping to local CRM contacts and their fact sheets.

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 usage: use this when you need a contact's fact sheet by handle. However, there is no explicit when-not-to-use or any mention of alternatives such as lookup_lead or crm_list_unread_messages, leaving room for confusion in a large sibling set.

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