conduyt_get_contact

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

With no annotations at all, the description carries the full disclosure burden. It usefully enumerates the payload (profile, tags, custom fields, timeline, deals, activity history), but says nothing about read-only safety, permission/scope requirements, error behavior for missing contacts, or whether those related sections are paginated or truncated.

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?

One front-loaded sentence with no filler; the enumeration of returned sections is load-bearing given there is no output schema. Slight length cost from the list, but every item earns its place.

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?

Because there is no output schema, the description's enumeration of return fields is necessary and present. But for a detail-fetch endpoint on a complex object, it leaves open whether related data (timeline, deals) is always included, limited in count, or expensive to retrieve.

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, and the schema already documents it fully as 'Contact UUID' (100% coverage). The description adds no format or sourcing guidance beyond what the schema states, so the baseline 3 applies.

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?

States a specific verb+resource ('Get a single contact'), and the word 'single' implicitly contrasts with conduyt_list_contacts and conduyt_search. It does not name a sibling explicitly, so it falls short of a 5.

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?

Usage is only implied: fetch one contact when you have its ID. There is no explicit statement of when to prefer this over conduyt_list_contacts or conduyt_search, and no note about prerequisites or what happens when the ID is unknown.

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