hubspot_resolve_id

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

No annotations are provided, so the description carries full burden. It discloses that the tool 'probes' the ID, implying a safe read operation, but does not explicitly state whether it is read-only or if there are any side effects. It lacks details about permissions, rate limits, or any observable effects.

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 extremely concise: two sentences for purpose and usage, then a clear one-line parameter description. Every sentence serves a purpose, and the most critical information (what the tool does) is front-loaded.

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 has an output schema (not shown but indicated by 'Has output schema: true'), the description need not detail return values. However, it could mention what the response includes (e.g., object type string). Overall, it is fairly complete for a simple resolver tool with clear input and purpose.

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 has 0% description coverage, so the description must compensate. It adds meaning by explaining that 'unknown_id' is 'The HubSpot numeric ID to probe', clarifying it is numeric despite being a string in the schema, and linking it to the use case. This is helpful but could specify format constraints.

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 it identifies the type of HubSpot object (deal, company, contact) that an ID belongs to, using specific verb 'identify' and distinct resource 'HubSpot object type'. This distinguishes it from sibling tools like hubspot_search_* or hubspot_get_* which retrieve or search existing data.

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 description explicitly states 'Use this when a lookup returns 404 and you're unsure whether the ID is a deal ID, company ID, or contact ID.' This provides clear context for when to use the tool. No exclusions or alternatives are mentioned, but the guidance is sufficient for decision-making.

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