get_hubspot_contact_object

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

No annotations are provided, so the description must carry full behavioral disclosure. It fails to mention that the query parameter defaults to '_most_recent_contact' for missing or short queries (though present in schema). It also omits details on return format, error handling, or read-only nature.

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, using one sentence that is front-loaded. However, it could benefit from slightly more structure to separate the two retrieval modes clearly.

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 no output schema, the description should clarify what 'contact data' entails. It does not specify return fields, pagination, or error behavior, leaving the agent underinformed for a tool with a required parameter.

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 description covers the parameter fully at 100% coverage. The tool description adds little beyond restating the purpose, 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 clearly states it retrieves contact data from HubSpot and distinguishes between query-based retrieval and fetching the most recent contact. This makes the purpose specific and distinct from sibling tools like get_hubspot_company_object.

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 implies usage contexts (query or most recent contact) but provides no explicit guidance on when to use this tool versus alternatives like get_person_object or contact_research. No when-not details are given.

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