fetch_hubspot_contacts

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

With no annotations, the description carries the full burden of disclosing behavior. It implies a read-only operation by using 'retrieves' and mentions auth context ('secure, synchronized OAuth credentials in Supabase'), but it does not state whether any data is modified, how the tool handles rate limits, or what constitutes 'active' contacts. This is limited transparency.

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 that is concise and front-loaded with the core purpose. The phrase 'CRM Data Fetcher' is somewhat redundant given the tool name, and 'Automatically' adds little, but overall it is efficient without unnecessary verbosity.

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?

The tool has an output schema, so return values are covered, but the description lacks crucial usage context such as parameter behavior and when to invoke it. Given the simple parameter set, the description is too sparse to be considered complete for an agent to reliably select and invoke the tool.

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 0% description coverage and the description does not mention the 'limit' parameter at all. Since the description must compensate for missing schema details and fails to do so, it provides no additional semantic meaning for the parameter.

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 retrieves active customer contacts from HubSpot using OAuth credentials in Supabase, providing a specific verb and resource. However, it does not explicitly distinguish itself from sibling tools such as ingest_realtime_webhook or export_to_data_warehouse, so it falls short of a 5.

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 gives no guidance on when to use this tool versus alternatives like ingest_batch_api_poll or retrieve_analytical_summary. It does not mention prerequisites, exclusions, or preferred scenarios, leaving the agent without usage context.

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