Collect CoDesign Network (Diagnostics)

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

The description goes beyond annotations by specifying that output never includes sensitive values (Cookie, Authorization, password, state-key) or response bodies—only JSON key paths. It also mentions the headless browser side-effect, aligning with the openWorldHint annotation.

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 sentences: first describes the core action, second explains use cases and output limitations. No wasted words, key information is front-loaded.

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?

The description covers main behavior and output redaction but omits details on the summary format and the effect of parameters like includeHeaders and maxBodyKeyDepth. Given no output schema, more detail would be helpful.

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?

With 0% schema coverage, the description should explain all five parameters, but it only mentions timeoutMs in context. It does not describe sharingUrl, password, includeHeaders, or maxBodyKeyDepth, leaving the agent to infer their roles.

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 tool opens a sharing page in a headless browser, records network responses for a specified timeout, and returns a redacted summary. This distinguishes it from sibling tools like login, logout, and artboard functions.

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 explicitly advises using this tool to discover unknown endpoints or debug tool failures. While it doesn't list when not to use it, the context makes it clear it's for diagnostic purposes rather than routine operations.

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