gorelo_get_contact

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

With no annotations, the description relies on the verb 'get' to signal a read-only operation with no side effects. It does not disclose what happens if the id does not match a contact or what fields the response will contain, but for a simple getter these omissions are relatively minor.

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 entire description is one short sentence, front-loaded with verb and resource, with no filler or redundant restatement of the tool name.

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 getter with no output schema, the description plus the schema's required id field is sufficient for selection and invocation. It could add what is returned or not-found behavior, but those are not essential to making the call.

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's id parameter has no description (0% coverage), so the phrase 'by id' is the only clue that the required number is the contact's unique identifier. This adds just enough meaning to invoke the tool, but it does not elaborate on id format or how to obtain it.

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 ('get') and identifies the resource ('single contact') and the access key ('by id'). This clearly differentiates it from the sibling gorelo_list_contacts, which returns a list rather than one record.

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 only usage cue is the phrase 'by id,' which implies the tool is appropriate when the caller already has a contact identifier. It does not explicitly mention that gorelo_list_contacts should be used to discover ids or state any exclusion conditions, so guidance is implied rather than explicit.

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