get_contact

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

No annotations provided, so the description carries full burden. It correctly describes the tool as a read operation (get details) and mentions the ability to include related data via the 'include' parameter. No side effects are implied, which is appropriate for a GET-like tool.

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?

Extremely concise and well-structured: three sentences, each with a clear purpose. The first sentence states the primary function, the second lists use cases, and the third explains a key parameter. No redundant information.

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 2 parameters, no output schema, and no annotations, the description covers the essential aspects: what it does, when to use, and how to use the include parameter. Could optionally mention return format or required permissions, but overall sufficient for effective tool usage.

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 100%, so baseline is 3. The description adds value by explaining the 'include' parameter's purpose (load related data in one request) and lists example values (children, documents, etc.), enhancing understanding 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 tool retrieves full details of a single contact by ID. It lists specific use cases (view before call, check relationships/documents/properties, see sub-contacts), distinguishing it from sibling tools like search_contacts or 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?

Provides explicit use cases (view before call, check related data) and mentions the 'include' parameter for loading related data. However, it does not explicitly state when not to use this tool or contrast with search_contacts for listing contacts, which would be helpful.

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