get_contact

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

The description is minimal but adequate for a simple retrieval: it indicates a read operation. However, it does not disclose what happens if the ID does not exist (error or null), nor any authentication or permission requirements. With no annotations, more detail would be helpful.

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—one sentence. It is front-loaded and efficient for a simple tool. However, could potentially include a brief mention of ID format or behavior without losing conciseness.

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 that an output schema exists (not shown), the description does not need to detail return values. But it omits error conditions, rate limits, or any prerequisites. For a simple get-by-ID tool with one param, it is mostly complete but lacks depth.

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 coverage is 0%, and the description adds no additional meaning to the lone parameter 'contact_id' beyond what the schema already provides (type integer, title 'Contact Id'). No format, constraints, or examples are given.

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 'Get a contact by ID' is precise: verb 'Get', resource 'contact', and method 'by ID'. It clearly distinguishes from sibling tools like list_contacts (lists multiple) and other get_* tools for different entities.

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 on when to use this tool vs. alternatives such as list_contacts or list_active_contacts. The description does not mention context or exclusions, leaving the agent without decision support.

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