ghl_kb_crawler_list_urls

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. Description adds HTTP method (GET) and version header, but does not disclose additional behavior like rate limits, permissions, or data volume. No contradiction with annotations.

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 concise sentences with no redundancy. First sentence states purpose, second adds endpoint and pagination context. Could be slightly more structured but is 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?

No output schema exists, and the description does not explain the return format (e.g., list of URLs, pagination metadata). It also omits mention of required parameters knowledgeBaseId and locationId. For a 5-param tool with no output schema, the description is insufficient.

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 100% with detailed parameter descriptions. Description mentions pagination params but adds minimal extra meaning beyond the schema (e.g., 'pass them to page through full result sets' hints at usage but is not substantial). Baseline 3 is appropriate.

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?

Description clearly states 'Get all trained page links by knowledge base', using a specific verb and resource. The title matches, and it distinguishes from sibling crawler tools (e.g., delete, discover) as a read-only list operation.

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?

Description provides endpoint details and pagination guidance ('pass them to page through full result sets'), indicating how to retrieve complete data. However, it does not explicitly contrast with alternative sibling tools like ghl_kb_crawler_discover.

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