centrex_get_contact

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

No annotations are provided, so the description must carry the full burden. It states the data returned (CRM fields, notes, metadata), which is helpful, but it does not disclose whether the tool is read-only, requires specific permissions, or has any side effects. The verb 'Get' implies a read operation, but explicit transparency is missing.

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 a single, front-loaded sentence with no wasted words. It immediately states the action and resource, making it highly efficient for an AI agent to parse.

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 required parameter, no output schema), the description adequately explains what the tool returns. However, it could be more complete by mentioning the return format (e.g., JSON object) or error handling. Still, it provides essential context for an agent to understand the tool's output.

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 input schema has 100% description coverage for the only parameter ('contact_id'), so the description adds no additional semantics beyond 'by ID'. The mention of 'including all CRM fields, notes, and metadata' refers to the return value, not the parameter. Baseline 3 is appropriate given the schema coverage.

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 action ('Get'), the resource ('a single contact by ID'), and the scope ('including all CRM fields, notes, and metadata'). It distinguishes this tool from sibling tools like 'centrex_list_contacts' (which returns multiple contacts) and mutation tools like 'centrex_create_contact'.

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 implicitly states when to use it (when you need full details of a single contact by ID), but it does not explicitly mention alternatives or when not to use it. For example, if only notes are needed, 'centrex_get_contact_notes' might be more appropriate. No exclusions or prerequisites are given.

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