hcp_list_lead_sources

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

The description discloses a useful behavioral trait not captured by annotations: 'Auto-paginates unless explicit page is set.' This adds meaningful context beyond the read-only, idempotent flags, though it does not address ordering, filtering, or response details.

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 the core purpose front-loaded and the pagination behavior immediately after. No filler or redundant restatement of the tool name.

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?

For a simple, read-only list operation with no required parameters and an output schema, the description is nearly complete. The main gap is the lack of usage guidance and page_size semantics, but the low complexity keeps this from being a significant deficiency.

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?

With schema description coverage at 0%, the description had to compensate for parameter meaning. It clarifies that setting an explicit 'page' disables auto-pagination, but it says nothing about 'page_size,' leaving its semantics to be inferred from the parameter name and type.

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 states a clear verb and resource: 'List lead sources.' It distinguishes the object from siblings like hcp_list_leads but does not explicitly differentiate itself from other list tools, 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?

No guidance is given about when to call this tool versus alternatives such as hcp_list_leads or hcp_list_customers. The auto-pagination note is behavioral, not usage-oriented, and there are no exclusions or alternate tool recommendations.

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