get_details_of_a_contact

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

No annotations exist, so the description carries full burden for behavioral disclosure. It only says 'Get a contact' with no details about permissions, return format, or how the contact is identified. This is critically insufficient for an agent to understand the tool's behavior.

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 short sentence, but it is under-specified. Conciseness should not sacrifice completeness; here, the sentence adds minimal value and does not earn its place due to lack of useful information.

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?

Despite low complexity (no parameters, no annotations, no output schema), the description is extremely incomplete. It fails to mention how the contact is identified, what details are returned, or any prerequisites. The agent has no way to use this tool correctly based solely on the description.

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?

There are 0 parameters and schema description coverage is 100%, so baseline is 3. The description does not add any parameter information (as none exist), but it could have clarified how the contact is selected (e.g., by ID). It meets the baseline but does not add extra value.

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' is essentially a tautology of the tool name 'get_details_of_a_contact'. It restates the action and resource without adding specificity, such as what 'details' are included or how it differs from similar siblings like 'contact_details'.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives (e.g., contact_create, contact_update, contact_search), nor does it mention any context or prerequisites.

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