get-contact

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

With no annotations, the description carries the transparency burden. It mentions 'full details' and 'including custom fields', which gives some behavioral context, but it does not disclose default behavior around the fields parameter or error handling. For a read operation, this is adequate but not comprehensive.

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, well-structured sentence that front-loads the verb and object, includes a specific detail (custom fields), and contains no unnecessary words.

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?

This is a simple read tool with only two parameters and no output schema. The description conveys the core functionality (return full details for a contact) and includes the custom fields nuance. However, it does not mention potential errors or response format, which would make it fully complete.

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 already describes both parameters (contact_id and fields) with 100% coverage. The description adds minimal value by mentioning 'custom fields', which hints at the fields parameter, but it does not explain the comma-separated format or 'all' option that the schema already documents. Baseline 3 is appropriate.

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 fetches full details for a single contact by ID, including custom fields. The verb 'get' and resource 'single contact' distinguish it from list-contacts and find-contact, which handle multiple or searched contacts.

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 implies the tool should be used when you have a contact ID and need full details, but it does not explicitly state when not to use it or mention alternatives like find-contact. No exclusions or prerequisites are provided.

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