Delete Website Source URL

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

Beyond the destructiveHint annotation, the description discloses that both the source record and its embeddings are deleted and that the operation is not reversible. It also specifies exact-match behavior and expected error codes (401/403, 404), which adds meaningful behavioral context.

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 well-organized with labeled sections (Requires, Auth, Errors, Related) and is front-loaded with the core purpose. However, the exact-match condition is stated twice in the opening, and list-v2 appears in both Requires and Related, creating minor redundancy.

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 2-parameter destructive operation with no output schema, the description covers prerequisites, destruction scope, irreversibility, auth modes, error handling, and related tools. Nothing critical is missing for an agent to invoke it correctly.

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 100%, and the parameter descriptions already explain the exact-match requirement and the B2B appId behavior. The tool description largely reiterates the schema, adding little new meaning beyond emphasizing 'get it from ethora-sources-site-list-v2'.

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 specific verb and resource: 'Remove a single crawled URL from an app's RAG sources.' It further clarifies exact-match semantics and explicitly distinguishes this tool from its batch sibling, so an agent can tell it apart without opening the schema.

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?

It names explicit prerequisites ('Requires: an indexed site URL from ethora-sources-site-list-v2... crawled with ethora-sources-site-crawl-v2'), auth requirements, and points to the bulk alternative `ethora-sources-site-delete-url-v2-batch`. This gives clear when-to-use and when-not-to-use guidance.

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