hubspot_get_object_notes

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

No annotations provided, so the description must disclose behavioral traits. It does not mention side effects, rate limits, authentication needs, or what happens if the object has no notes. The description is too minimal for a mutation-purpose tool (though read-only, it doesn't confirm idempotency or safety).

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?

One sentence, no wasted words, but too brief. Lacks structure and fails to include important information like return format or parameter usage. It is concise but not sufficiently informative.

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?

No output schema, so the description should explain the return value (e.g., list of notes with fields). It does not. Given the large set of sibling tools, more differentiation and examples would be helpful. The description is incomplete for an agent to understand what to expect.

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 67%, but the description adds no new meaning to parameters beyond the schema. It repeats the objectType enum values but does not explain the limit parameter or clarify how objectId is used. The description does not compensate for the lack of parameter detail.

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 tool gets notes associated with a HubSpot object and lists the supported object types (contact, company, deal, ticket). This distinguishes it from sibling tools like hubspot_get_note (single note) and hubspot_list_notes (all notes).

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 on when to use this tool over alternatives, such as hubspot_search_notes or hubspot_get_note. No context about prerequisites or scenarios where it is not appropriate.

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