get_contact

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds no extra behavior details—it simply restates the name without mentioning return format, error handling, archived behavior, or any other operational nuance.

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 extremely short, but under-specification is not conciseness. The sentence restates the tool name and does not earn its place by providing useful information, making it more of a label than a helpful description.

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?

The tool is a simple get-by-id operation with good annotations and schema coverage, but the description is too minimal to be complete. Since there is no output schema, the description should at least imply the return type or clarify the uniqueness of the ID lookup, but it does neither.

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 for both parameters (contact_id and show_archived), so the baseline is 3. The description 'Fetch a contact' adds no additional meaning beyond the schema and does not even mention the required contact_id.

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 uses a specific verb 'Fetch' and a clear resource 'contact', indicating it retrieves a single contact. However, it does not differentiate from sibling tools like search_contacts or list_contacts, though the schema's required contact_id implies one-by-ID retrieval.

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 provides no guidance on when to use this tool versus alternatives such as search_contacts, list_contacts, or get_contact_group. There are no context cues, exclusions, or alternative recommendations.

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