ghl_delete_crawler_urls

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

No annotations are provided, so description bears full responsibility. It unambiguously states the destructive action and return value, but does not disclose whether deletion is permanent, requires permissions, or handles partial failures. Adds minimal behavioral context beyond the verb 'Remove'.

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, front-loading the action and resource, then giving a usage hint and return value. No wasted words.

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?

Simple 2-param tool with explicit return value in description. Missing details like error behavior or irreversibility are notable but not critical for a straightforward delete operation within a knowledgeable domain.

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 descriptions already fully document both parameters (knowledgeBaseId and urlIds, including how to retrieve urlIds). Description adds no new semantics beyond what the schema provides. Baseline 3 applies with 100% schema coverage.

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 uses specific verb 'Remove' and identifies resource 'trained page URLs from a knowledge base'. It clearly distinguishes from sibling tools like ghl_list_crawler_urls and ghl_train_crawler_urls by indicating a deletion 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?

Provides clear context that urlIds should come from ghl_list_crawler_urls, which is a helpful usage hint. It does not explicitly mention alternatives or when-not-to-use, but the list reference implicitly guides correct usage.

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