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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds crucial context beyond these: the required permission, server-side tag-scope enforcement, opt-in relation flags to control response size, and pagination with has_more. No contradiction with annotations.

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 well-structured with clear sections: purpose, filters, relation flags, pagination, and an example. It is concise despite covering many parameters, using bullet points to avoid verbosity. The example is illustrative and the whole is easily scannable.

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?

Despite 13 optional parameters and no output schema, the description explains every aspect needed for correct invocation: filter options, relation flags, pagination mechanics, and permission requirements. It also hints at response shape via meta.pagination.has_more. For a read-only listing tool, this is comprehensive.

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 coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining tag slugs (stable hyphenated form vs spaces), status based on latest ping, search being case-insensitive substring over label+ip, pagination defaults (25, max 200) and the has_more indicator, plus a concrete usage example. This goes well beyond what the schema provides.

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 states a specific verb (List) and resource (monitored devices), and adds the HTTP endpoint and permission. It is clearly distinct from sibling tools like device_get (specific device) or device_find (search) by focusing on listing with filters and relations.

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 detailed usage instructions including optional filters, relation flags, and pagination behavior, but does not explicitly name when to use this tool versus alternatives like device_get or device_find. The context strongly implies listing vs. lookup, but an explicit exclusion would be stronger.

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