list_network_devices

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

No annotations are provided, so the description must disclose behavioral traits. It mentions filtering and pagination but does not elaborate on how they work, what happens with large result sets, rate limits, or that the operation is read-only (implicit but not stated). The description is too terse to provide adequate 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 filler words. It is front-loaded with the verb and resource and efficiently conveys the core purpose and features. Every word earns its place.

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?

No output schema is provided, and the description does not mention return format, field details, or usage examples. For a list tool with four optional parameters and no required fields, the description lacks enough context to fully specify tool behavior. It leaves agents guessing about how to effectively use filtering and pagination.

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 0%, so the description must compensate. It connects 'filtering' to filter_tag and 'pagination' to page_size/page_number, and implies sort is used for sorting. This adds some meaning beyond bare names, but does not explain valid values, format, or default behavior. A score of 3 reflects marginal added value.

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 verb 'List', the specific resource 'network devices monitored by Datadog NDM', and mentions key features 'filtering and pagination'. It effectively distinguishes from the many sibling list tools that target different resources (e.g., list_containers, list_workflows).

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?

No explicit guidance on when to use this tool versus alternatives. While the resource name implies its domain, there is no mention of prerequisites, when not to use it, or comparison with other list tools. The description is purely declarative.

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