cluesift_domain_fetch

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The only behavioral hint is 'best-effort', implying possible delivery failure, but it does not explain error handling, retries, output format, or side effects. This leaves significant transparency gaps.

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 a single, concise sentence with no redundant wording. It delivers the primary purpose upfront, but its brevity comes at the cost of missing critical details, so it is efficient yet under-specified.

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?

With four required parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain the full workflow, the role of each parameter, the destination of the fetched page, or how the agent should handle failures. This tool cannot be invoked confidently based on the description alone.

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?

The input schema has 0% description coverage, and the tool description does not explain any of the four required parameters (url, artifact_target, request_id, case_id). The description adds no meaning beyond what the schema already shows, which is just types and an enum, leaving the agent without context for request_id and case_id.

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 clearly states the core action ('Fetch a public page and best-effort deliver it to a fixed ClueSift target'), which distinguishes it from siblings like web_fetch or web_search. However, 'fixed ClueSift target' is ambiguous given the artifact_target parameter, which can be 'cluesift-test' or 'cluesift-prod'.

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 provided on when to use this tool versus the sibling tools (web_search, web_fetch). There is no mention of prerequisites, exclusions, or recommended use cases, leaving the agent to infer usage from the name and description alone.

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