diagnose_discovery

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

With no annotations, the description carries the transparency burden. The verb 'Explain' implies a read-only, non-destructive operation, and 'without asking users for technical setup' suggests no user-side side effects. However, it doesn't explicitly state that it makes no changes or what state it accesses, leaving some ambiguity for a diagnostic tool.

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 that front-loads the main purpose and the key constraint. Every word adds value; there is no redundancy or padding.

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 0-parameter tool with no output schema, the description adequately covers the core purpose: explaining discovery state and next steps. It could elaborate on what 'current discovery state' encompasses, but it's sufficient for an agent to understand the tool's role.

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 tool has zero parameters, so the description doesn't need to add parameter details. Per the baseline for 0-param tools, this scores a 4.

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 specifies the action ('Explain'), the resource ('current discovery state'), and the deliverable ('next checks'). It distinguishes this tool from siblings like discover_devices (which performs discovery) and list_known_devices (which lists results) by focusing on explanation rather than action.

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 phrase 'without asking users for technical setup' provides a clear usage context: use this tool when you need to explain state without involving the user in technical tasks. It doesn't explicitly mention alternatives or exclusions, but the context is well-defined.

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