list-fleet-agents

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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is lighter. The description adds that the tool supports filtering, sorting, and pagination, which is useful but lacks specifics (e.g., default page size, sorting defaults). It adequately supplements annotations without contradicting them.

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, well-structured sentence that front-loads the action and resource, then enumerates capabilities. No fluff or repetition, earning the highest score.

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 list tool with a well-described schema and annotations, the description provides adequate high-level context. It covers the main operations (filter, sort, paginate) without needing to detail output (no output schema). Slight gap: no mention of what the response contains, but still functional.

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% and each parameter already has a clear description (e.g., pageNumber is 0-based, pageSize max 100). The description adds no additional meaning beyond restating these capabilities, so baseline 3 is appropriate.

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 verb 'List' and the resource 'Datadog Agents in the fleet', distinguishing it from sibling tools like list-fleet-deployments or list-hosts. It also mentions key capabilities (filtering, sorting, pagination), making the purpose immediately clear.

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?

There is no explicit guidance on when to use this tool vs alternatives. While the resource is clear, the description does not state when not to use it or provide context about alternatives among the many list-* siblings.

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