hs_list_lists

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

No annotations are provided, so the description carries full burden. It mentions listing all lists but does not disclose behavioral traits such as read-only nature, rate limits, authentication requirements, or what happens with no results. For a listing tool, this is insufficient.

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?

Two short sentences with no redundancy. The core purpose is front-loaded, and every word adds value. Highly efficient.

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 description covers the basic operation but lacks details on return format, pagination behavior, and limit semantics. Since there is no output schema, the description should compensate but fails to describe the response structure, making it incomplete for an agent to fully understand the output.

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 50% (query has description, limit does not). The description adds a phrase 'Optionally filter by name substring' which reinforces the query parameter but adds no new meaning beyond the schema. The limit parameter is not described, leaving the agent unclear about its effect.

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 lists all HubSpot contact lists (static and active) with optional name filtering. The verb 'list' and resource 'HubSpot contact lists' are specific. However, it does not explicitly differentiate from sibling tools like 'hs_get_list' (single list) or 'hs_crm_search', though the tool name suggests plural.

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 usage when you want to retrieve all contact lists, but no explicit guidance on when not to use this tool or alternatives. Siblings like 'hs_get_list' exist for single list retrieval, but no reference is made.

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