get_contact

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read operation via 'Get' and suggests completeness via 'full details', but does not disclose error behavior (e.g., not found), authentication requirements, or whether it modifies anything. For a simple read tool this is minimally acceptable but lacks depth.

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 conveys the essential purpose and key qualifier immediately, making it highly readable and efficient.

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 simple single-parameter read tool with no output schema, the description is sufficiently complete to set expectations: a full contact record returned by ID. It leaves room for ambiguity about the exact fields, but the simplicity of the operation makes this acceptable.

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 100% coverage with the parameter description 'Contact ID', so the baseline is 3. The tool description adds no further meaning beyond restating that the lookup is 'by ID'—no format, types, or additional context is given beyond the schema.

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 full details') and resource ('contact') with the key qualifier 'by ID', making the purpose unambiguous. It implicitly distinguishes from sibling tools like list_contacts (which lists multiple contacts) and get_ticket (different resource), but does not explicitly name alternatives.

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 phrase 'by ID' implies this tool is for retrieving a single contact when the ID is known, which is a clear usage context. However, it does not explicitly state when not to use it or name alternatives like list_contacts, leaving the guidance at an implied level.

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