list_directory_devices

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clarifies the important scope distinction (directory vs. Intune-managed), which is useful, but it does not mention output shape, pagination, or how top/filter interact with the result set. The 'List' verb implies a read-only operation, and the scope clarification adds meaningful value beyond the name.

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 that front-loads the core purpose and adds a key distinction. There is no wasted text, and the scoping information is placed immediately after the verb and resource.

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 simple list tool with two optional parameters and no output schema, the description provides the essential selection-level context. However, an agent invoking with 'filter' or 'top' would need to infer their semantics, and the return format is not described. It is minimally viable but not fully complete.

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, but it does not mention 'top' or 'filter' at all. The parameter names are somewhat self-explanatory (top likely limits results, filter likely filters), but no syntax, defaults, or behavior are described.

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 uses a specific verb ('List') and a clear resource ('directory (Entra) devices'), and immediately contrasts it with 'Intune-managed devices.' This distinguishes the tool from the sibling list_managed_devices without needing to open either schema.

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?

The description gives clear context for when to use this tool: when directory/Entra devices are needed. It also provides an explicit when-not signal ('not Intune-managed devices'), but it does not name the alternative tool for Intune-managed devices, so it falls just short of a fully explicit routing instruction.

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