Get Contact

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

The description adds only 'full contact record' beyond the readOnlyHint annotation. It does not discuss error states, permissions, or response format, which is acceptable given the annotation covers safety, but minimal added value.

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, efficient sentence that immediately states the purpose. Every word earns its place with no redundancy or fluff.

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 the simple input schema, the presence of an output schema, and the readOnlyHint annotation, the description is mostly complete for a basic get-by-id operation. It lacks details on error handling or permissions but is generally sufficient.

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 0%, and the description only says 'by id', which weakly hints that contact_id is the identifier. No format, example, or additional meaning is provided, failing to significantly compensate for the lack of schema descriptions.

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 verb 'Get', the resource 'full contact record', and the method 'by id'. It distinguishes itself from sibling tools like contacts_create, contacts_delete, and contacts_search by being the dedicated lookup tool.

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?

No guidance is provided on when to use this tool versus alternatives like contacts_search. There is no mention of prerequisites or exclusions, leaving the agent to infer context from the name alone.

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