Retrieve a public manifest or document from DDG using its ID or ddg:// URI, with automatic redaction and size limits.
Fetch an allowlisted DDG public manifest/doc by id or ddg:// URI with redaction and size caps.
| Name | Required | Description | Default |
|---|---|---|---|
| resource | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description solely carries the burden of behavioral disclosure. It mentions 'redaction and size caps' but does not explain what they entail, whether the operation is read-only, or how errors are handled for non-allowlisted resources.
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, front-loaded sentence with no redundant words. However, it could be expanded slightly without sacrificing conciseness to cover missing details.
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?
Given the tool has one required parameter and no annotation, the description omits output expectations, error scenarios, and the impact of size caps/redaction. The presence of an output schema does not fully compensate for missing explanations.
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 0% so the description must compensate. It suggests the parameter accepts an id or ddg:// URI but does not specify format, validation, or examples. The single parameter 'resource' remains ambiguous despite the hint.
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 'Fetch' and identifies the resource as 'allowlisted DDG public manifest/doc', clarifying both the action and the object. It distinguishes from sibling 'ddg_public_resource_index' which lists resources, so the purpose is clear.
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?
The description does not provide any explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites like obtaining an ID or URI from an index. The context is implied but not directly stated for an AI agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.