get_contact

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the operation is a read ('Get') and promises the 'complete record', but it doesn't disclose edge cases such as not-found behavior or authentication requirements. The disclosure is adequate for a simple read but lacks depth.

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, front-loaded sentence starting with the action verb 'Get'. It contains no filler and communicates the entire purpose efficiently.

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?

For a simple retrieval tool with one parameter and no output schema, the description covers the essential function. It could be enhanced by describing the response structure or error behavior, but the core purpose and invocation are clear.

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 schema offers only the parameter name 'contact_id' with no description (0% coverage). The description compensates by explaining the parameter is the Elorus ID, giving it essential semantic meaning beyond the raw 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 uses the specific verb 'Get' and identifies the resource as a contact, clarifying it retrieves a single record by its Elorus ID. This clearly differentiates it from sibling tools like list_contacts, which retrieve collections.

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 phrase 'by its Elorus ID' clearly indicates the tool is for when you have a specific contact ID, providing clear context for use. It does not explicitly name alternatives like list_contacts, but the purpose distinction is strongly implied.

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