hubspot.v2.search_objects

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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, authentication requirements, rate limits, or side effects. For a search tool, it is likely safe but this is not stated, leaving the agent uninformed.

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 brief (2 words), which is under-specified. It does not front-load important information or structure details. Conciseness is not beneficial when it sacrifices completeness; every sentence should earn its place, and this description lacks substantive content.

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's complexity (8 parameters, many sibling tools, no output schema), the description is completely inadequate. It does not explain return values, pagination, sorting behavior, or how it relates to other HubSpot tools. The agent is left without essential context.

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 input schema has 8 parameters but only 25% have descriptions. The description does not add any parameter information beyond the schema. For example, the 'filters' parameter lacks explanation of its format or usage. The description fails to compensate for the low schema coverage.

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 'Search HubSpot Objects' clearly states the action (search) and resource (HubSpot objects), but it does not differentiate from sibling tools like hubspot.v2.lookup_object or the general 'search' tool. The purpose is somewhat vague as it doesn't specify what kind of search or what objects are included, though the schema enum provides some context.

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 versus alternatives. There is no mention of prerequisites, context, or exclusions. The description lacks any usage direction, making it difficult for an agent to decide between this and other search-related tools.

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