reach_getContactDetailsV1

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

No annotations are present, so the description carries the full burden. It usefully discloses that tags and custom contact field values are included, but it does not mention error behavior, permissions, or explicitly confirm read-only semantics. No contradictions with annotations (none provided).

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?

Two short sentences, front-loaded with the main purpose. The second sentence adds relevant return-value detail without redundant phrasing.

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-contact getter with two parameters and no output schema, the description adequately explains the main return content. It could be more explicit about error handling or the UUID relationship, but overall is complete for typical use.

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, so a baseline of 3 applies. However, the parameter descriptions are tautological ('Contact uuid parameter'), and the tool description adds no additional meaning about the relationship between profileUuid and contactUuid.

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 'Get the full details of a single contact,' clearly stating the specific verb and resource. It further specifies the response includes tags and custom contact field values, which distinguishes it from list/update/delete contact tools among siblings.

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 'single contact' implies use when you need one contact's full details rather than a list. This provides clear context, though it does not explicitly name alternative tools or exclusion scenarios.

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