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

With no annotations, the description carries the behavioral disclosure burden. It does this well by explaining that free/free-trial services return results directly while paid services return an x402 challenge, and by specifying the settle-and-retry flow. It does not mention auth prerequisites beyond the payment headers or what happens on invalid service names, but 'Only known DDG catalog paths are accepted' partially covers that.

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 three tight sentences with no filler. The core purpose is front-loaded, followed by the critical payment behavior, and ends with the discovery constraint. Every sentence earns its place.

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 generic executor over a large catalog, the description covers the essential operational facts: how to target a service, how to discover valid targets, and how paid versus free responses behave. An output schema exists, so return-value details are not required. The main gaps are the unexplained 'agent_id' parameter and the lack of explicit guidance to prefer specialized siblings when available.

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 0%, so the description must compensate. It does add meaning to 'service' by saying it accepts a service_id or /v1/ path, and it clarifies that 'args' are JSON. However, 'agent_id' is entirely undocumented, and no concrete example of a service identifier or args payload is given, so parameter guidance is only partial.

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 opens with a specific verb and resource: 'Invoke any DDG service by service_id or /v1/ path with JSON args.' It also frames the tool as a 'generic executor over the whole DDG catalog,' which clearly separates it from the many specialized ddg_* sibling tools.

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 explicitly tells the agent how to discover valid targets ('use ddg_search_services(need) to discover valid targets') and notes that only known catalog paths are accepted. It also explains the free-vs-paid behavior, which affects whether retries are needed. However, it does not explicitly tell the agent to prefer a specialized sibling tool when one exists, so an agent might overuse this generic executor.

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