smokeball_get_contact

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits like read-only, side effects, or authentication needs. It only mentions generic routing through the API, offering no substantive behavioral context beyond the tool name.

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 relatively short but includes boilerplate routing information that is unnecessary for understanding the tool's purpose. It is front-loaded with the name but contains some redundancy, making it average in 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 the tool's simplicity (one parameter) and the presence of an output schema, the description should at least clarify how to construct the 'arguments' string. It fails to do so, leaving a significant gap in input specification.

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 sole parameter 'arguments' is a JSON string with 0% schema description coverage. The description does not explain what keys or values to include (e.g., contact ID), providing no additional meaning beyond the schema's terse definition.

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 states it's a 'get_contact' operation, which clearly indicates retrieving a contact. Among siblings like 'smokeball_create_contact' and 'smokeball_list_contacts', it distinguishes as a single-get tool. However, it lacks detail on what a contact is or what the tool returns, making it only moderately clear.

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 is provided on when to use this tool versus alternatives such as 'smokeball_list_contacts' or 'smokeball_search'. The description does not mention prerequisites, 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.