list_network_devices

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

Mentions filtering and pagination, which are key behaviors, but does not disclose other traits like rate limits, latency, or what happens with empty results. With no annotations, more detail is expected.

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?

Single sentence, front-loaded with verb and resource, no unnecessary words. Efficient for a list tool.

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 4 parameters, no annotations, and no output schema, the description is too sparse. Missing details on return format, error handling, default sorting, or pagination limits.

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%, and the description only hints at filtering and pagination without mapping to specific parameters (page_size, page_number, filter_tag, sort). Adds minimal value over the raw schema.

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 lists network devices monitored by Datadog NDM, with a specific verb and resource. It distinguishes itself from sibling tools like list_aws_accounts or list_hosts by being explicitly about network devices.

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 guidance on when to use this tool versus alternatives (e.g., get-hosts or list-fleet-agents). Missing when-not-to-use or prerequisites like authentication or monitoring setup.

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