List leads

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

No annotations are provided, so the description alone must disclose behavior. It reveals only that results are paginated; it does not state read-only status, default page size/page number, behavior with no arguments, or whether search filters server-side or client-side. This is minimal behavioral disclosure.

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 very short and front-loaded, with no filler words. However, it is mostly a repetition of the title with only '(paginated)' as new content, and it lacks enough structure to qualify as a genuinely helpful definition.

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 tool with three optional parameters, no output schema, and no annotations, this description is under-specified. It omits search semantics, pagination defaults, result format, and any guidance about large result sets. An agent can issue the call but cannot fully predict or control its behavior.

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 does not explain 'search', the meaning of pageSize/pageNumber, or pagination defaults. The parenthetical 'paginated' hints at the pagination parameters but adds no semantic detail beyond what the schema already shows.

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 uses a specific verb and resource ('List leads') and adds the key qualifier 'paginated'. Among the many sibling list_* tools, the resource name clearly differentiates this operation. However, it doesn't describe the lead scope, filters, or return shape, so it falls short of a full 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?

There is no guidance on when to use this tool vs alternatives, no exclusions, and no mention of complementary tools like gambot_get_lead or gambot_create_lead. With dozens of sibling list tools, an agent gets no routing help beyond the resource name.

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