holded_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 only states the operation and does not confirm read-only behavior, error handling, authorization requirements, or response characteristics. For a getter there are no destructive side effects implied, but the description does not state this explicitly.

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?

A single sentence that front-loads the verb and resource, contains no filler, and communicates the essential input and output expectation. Every word contributes to meaning.

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 one-parameter get-by-ID tool, the description plus schema provide enough to invoke it correctly. The absence of an output schema and annotations is a minor gap, as the return shape and error behavior are not described, but the tool is simple enough that this does not critically block usage.

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 already documents contactId with 'ID del contacto' (100% coverage). The description's 'por su ID' simply repeats the same concept without adding format, constraints, or usage nuance beyond what the schema provides.

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 ('Obtiene') and resource ('detalle de un contacto específico') and specifies the lookup key ('por su ID'). This clearly distinguishes it from sibling tool holded_list_contacts, which returns a collection rather than a single entity.

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 tool's purpose is self-evident: it is used when the agent has a contact ID and needs the full detail of that one contact. It does not explicitly name alternatives or exclusions, but the context is clear enough for correct selection among the sibling tools.

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