hubspot_search_notes

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

No annotations are provided, so the description carries full burden. It only states 'by content or properties' but does not disclose behaviors like pagination (though after/limit exist in schema), authentication requirements, or how filters interact. The description adds minimal behavioral insight beyond the schema.

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 a single sentence of 8 words, which is highly concise. It is front-loaded with the core action. However, it sacrifices informativeness for brevity, lacking any structure that could aid understanding.

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 has 5 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the return format, how to handle edge cases, or how the parameters work together. The tool's complexity demands more detail.

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 only 40%, meaning many parameters lack descriptions in the schema. The description 'by content or properties' vaguely hints at query and filters but does not explain any parameter semantics. For example, it doesn't clarify what 'properties' means or how to construct filters. The description barely compensates for the low 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 notes in HubSpot by content or properties' uses a specific verb ('Search') and resource ('notes'), clearly distinguishing it from sibling tools like hubspot_list_notes (which lists all notes) and other search tools for different entities (e.g., hubspot_search_calls).

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 explicit guidance on when to use this tool over alternatives. While sibling tools exist for similar operations on different entities, the description does not mention conditions or exclusions. It provides no context for when to choose search over list or other operations.

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