hubspot_get_contact

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

The description is minimal ('Get a contact by ID from HubSpot') and adds little beyond the tool name. No annotations are provided. It does not disclose any behavioral details such as what data is returned, potential errors, or whether any side effects occur. For a read operation, this is marginally acceptable but still lacking.

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 sentence of 7 words, which is very concise and front-loaded. However, it is overly minimal and does not provide sufficient detail for a tool that has two parameters and no annotations. Conciseness should not come at the expense of completeness.

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 that there is no output schema and no annotations, the description should provide more context about what the tool returns, any limitations, or additional behavior. It is incomplete for an agent that needs to understand the tool's full capabilities and constraints. A simple get operation might be straightforward, but the lack of any details reduces completeness.

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?

Schema coverage is 100% (both parameters have descriptions), so the baseline is 3. However, the tool description does not add any meaning beyond the schema. It merely restates 'by ID' which aligns with the 'contactId' parameter. The 'properties' parameter is not elaborated in the description, missing an opportunity to clarify its usage.

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 clearly states the action ('Get'), the resource ('a contact'), and the context ('from HubSpot'). It is a specific verb+resource combination. However, it does not differentiate itself from sibling tools like 'hubspot_search_contacts' or 'hubspot_list_contacts', which also retrieve contacts.

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. There is no mention of prerequisites, exclusions, or specific scenarios. The agent must infer from the name that it is for fetching a single contact by ID, but no comparative context is given.

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