fetch_hubspot_contacts

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

With no annotations, the description must disclose behavioral traits. It mentions OAuth authentication but fails to explain the 'limit' parameter, what 'active' means, or any pagination or rate limiting behavior. This is insufficient for a mutation-free fetch operation.

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 with a clear label 'CRM Data Fetcher:', making it concise and front-loaded. However, the colon separates the label from the explanation, which is minor but acceptable.

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 simplicity of the tool (one optional parameter) and presence of an output schema, the description covers the basic purpose but omits details like pagination behavior and the meaning of 'active'. It is adequate but not comprehensive.

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 0%, and the description adds no meaning to the 'limit' parameter beyond the schema. The parameter is not mentioned, failing to compensate for the low coverage. Baseline for low coverage requires description to add value, which it does not.

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 active customer contacts from HubSpot, specifying the verb 'retrieves' and the resource 'contacts'. It distinguishes well from siblings like ingest_realtime_webhook and export_to_data_warehouse, which handle data ingestion and export respectively.

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 use for fetching contacts but lacks explicit guidance on when to prefer it over alternatives or situations to avoid. No direct comparison to sibling tools is provided.

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