datadog_hosts_list

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

Describes pagination (limit=0 auto-paginates to 10000) and output format (YAML), adding value beyond absence of annotations. Does not explicitly declare read-only or rate limits, but no contradictions.

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?

Three sentences, each adding distinct value: purpose, pagination behavior, and output format. No fluff, front-loaded with primary action.

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?

Covers purpose, pagination, and output well. Lacks error handling or rate limit info but is sufficient for a simple list tool with full schema coverage.

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?

Adds meaning beyond schema by explaining auto-pagination rule for limit parameter and specifying YAML output. Schema already covers filter and from descriptions.

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?

Clearly states 'List Datadog reporting hosts' with specific verb and resource. Differentiates from siblings like datadog_dashboard_list by explicitly naming 'hosts'.

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?

Details auto-pagination behavior and output format, but does not explicitly state when to avoid this tool or mention alternatives like search tools for finer-grained queries.

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