Devices Needing Attention

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, establishing this as a safe, read-only operation. The description adds no further behavioral context (e.g., what 'flagging' means, data recency, or rate limits). It is adequate but does not enhance transparency.

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 sentence with no extraneous information. It is concise and front-loaded, but the brevity sacrifices completeness. Nonetheless, it avoids fluff.

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's complexity (3 parameters, no schema descriptions, but an output schema exists), the description is too minimal. It does not explain the context of 'devices needing attention' or how the parameters influence behavior. The agent lacks sufficient context to use the tool effectively.

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 input schema has 3 parameters (group_id, limit, output_format) with no descriptions (0% coverage). The description does not explain these parameters or their effect on results. The agent must guess from names or rely on schema structure, which is insufficient for proper invocation.

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 'Surface' as a verb, which is vague and not a standard action. It indicates the tool returns devices flagged for immediate action but lacks specificity on what constitutes 'flagged' or how this differs from other device listing tools. The purpose is partially clear but could be more precise.

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 provides no guidance on when to use this tool versus the many sibling tools (e.g., list_devices, search_devices, device_detail). It does not state prerequisites or scenarios where this tool is preferred, leaving the agent without decision support.

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