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

readOnlyHint already establishes the safety profile, and the description adds genuine behavior beyond it: the default bounded 30-day window, the portal-selection rule, the instruction to cite returned record URLs, and a caveat that partial history does not imply an overdue task. Return format and pagination remain undisclosed.

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?

Front-loads the purpose before routing and constraints, and each sentence adds a distinct piece of information (usage, portal rule, default window, citation, interpretation caveat). Slightly dense but no wasted sentences.

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?

With only a readOnlyHint, 5 undocumented parameters, and no output schema, the description does most of the work: defaults, portal selection, contact-scoped lookup, and output citation are all covered. The gap is that kind/limit semantics and return shape are never addressed, so it is not fully self-sufficient.

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 0% across 5 parameters, so the description carries the full burden. It meaningfully explains days (default 30-day window), portal_id (one portal when several are connected), and contact_id (later activity for a specific person), but says nothing about kind or limit, leaving two parameters undocumented.

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?

States a specific verb (Read) and resource (recorded notes, emails, calls, meetings, tasks in the user's connected HubSpot portal), which clearly separates it from ask_about_hubspot_* and get_hubspot_summary. It never explicitly contrasts with the closest sibling search_hubspot_crm, so an agent must infer the boundary.

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?

Gives concrete usage context ("for follow-ups, explicit next steps, and supporting activity") and a prerequisite ("Select one portal when several are connected"). There is no when-not-to-use guidance or named alternative, so it stops short of a full routing statement.

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