List devices

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

Discloses pagination behavior and SQL LIKE matching with wildcard syntax. No annotations, so description carries full burden; it covers read-only nature implicitly.

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 concise sentences, front-loaded with purpose, then filter details, then pagination. No redundant information.

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 essential context: pagination and filter behavior. No output schema, but hints at pageDetails. Could mention response includes device list explicitly.

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 covers all params (100%), description adds value by explaining wildcard usage in LIKE matching and pagination response details.

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 all devices in the account' with optional filters, distinct from sibling tools like datto_get_device or datto_list_site_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?

Implied usage for account-wide listing with optional filters, but no explicit guidance on when to use vs. alternatives like datto_list_site_devices.

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