discover_dtd_uris

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

With no annotations, the description carries the full burden. 'Discover running' implies a non-mutating probe, but it doesn't disclose that the tool scans ports (the timeout parameter hints at this), how long it may take, or that it can find zero daemons. It conveys the operation's nature but not its cost or failure behavior.

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 short sentences, purpose front-loaded, with the second sentence supplying useful downstream context. No padding, though the downstream detail is more helpful to a human than to an agent deciding whether to invoke.

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?

An output schema exists, so return-value explanation is not needed, and a one-parameter read tool has few remaining gaps. The description covers what it does and where the results go; only invocation triggers and empty-result handling are absent.

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 single timeout parameter is fully documented in the schema, so the baseline of 3 applies. The description adds no syntax, units, or tuning advice beyond what the schema already says.

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?

States a specific verb and resource: 'Discover running Dart Tooling Daemon (DTD) URIs'. The domain (Flutter debugging) is explicit and unambiguous, and it is trivially distinguishable from every sibling, all of which are mobile UI-automation 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 gives downstream context (the URIs feed connect_dart_tooling_daemon for hot reload and widget inspection), which implies when the tool is useful, but it never states a trigger condition or any when-not guidance, nor what to do if discovery returns nothing.

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