chatwoot_get_contact

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds little behavioral context beyond that, such as no mention of pagination, rate limits, or error behavior; however, it does not contradict the annotations and the simple read-only nature lowers the burden.

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 core purpose before the Args block. The only waste is the tautological 'output_format: Output format.', which is a minor flaw in an otherwise lean definition.

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 read-only getter, the description plus annotations and output schema are largely sufficient. It includes how to source the required contact_id, and the output schema can cover return details, so nothing critical is missing for a correct call.

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 0%, so the description must compensate. It adds real meaning to contact_id by instructing the agent to use chatwoot_search_contacts to get IDs, but output_format is merely called 'Output format', adding no value beyond the schema's enum.

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 opens with a clear verb and resource: 'Returns the full details of a specific contact.' It also distinguishes itself from the search sibling by telling the agent to use chatwoot_search_contacts for IDs, so there is no ambiguity about which tool fetches a single 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 explicitly points to chatwoot_search_contacts as the way to obtain contact_id, which is a concrete alternative and usage route. It does not state when not to use this tool versus other contact-related siblings, but the single-contact purpose is clear.

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