hubspot_get_contact

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

With no annotations, the description carries full burden for behavioral disclosure. It only mentions 'READ-ONLY' but omits other traits like error handling, rate limits, or data freshness. The description is minimal.

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 succinct, with a clear header and structured Args section. No filler words. However, it could be more concise by omitting the re-statement of parameter names in the description since they appear in the schema.

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 simple read-only tool by ID, the description covers purpose and parameters. An output schema exists, so return values need not be described. Minor gaps: no usage guidance or behavioral details, but the tool is straightforward.

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 description coverage is 0%, but the description adds meaning: 'contact_id: HubSpot contact ID' and 'properties: Comma-separated properties to return'. However, it does not specify the format of contact_id or any constraints, so baseline 3 is appropriate.

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 explicitly states the verb 'Get', resource 'HubSpot contact', and method 'by ID'. It also notes 'READ-ONLY'. Among sibling tools like hubspot_search_contacts, this tool's purpose (direct retrieval by ID) is unmistakably 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?

The description provides no guidance on when to use this tool versus alternatives. For instance, it does not contrast with hubspot_search_contacts or other lookup tools, nor does it specify prerequisites or context for use.

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