list_device_posture_rules

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool lists posture rules and adds a definition, but does not mention authentication needs, account scope, read-only nature, pagination behavior, or any response characteristics. 'List' implies read-only, but beyond that the behavior is opaque.

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 concise sentence with no wasted words. The core action and object are front-loaded, and the parenthetical adds useful clarification without padding. It is a model of efficient writing, even if other dimensions lack depth.

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?

This is a simple tool with one documented parameter, but there is no output schema and no annotation context. The description explains what the resource is but does not mention what the returned data looks like, how many rules may be returned, or any account-level caveats. It is minimally viable but leaves an agent without important operational context.

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 100%, with the only parameter, account_id, already described as 'The account ID'. The description adds no additional meaning about how account_id should be used, so the baseline of 3 is appropriate because the schema carries the parameter documentation burden.

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 resource ('device posture rules') and adds a clarifying parenthetical ('compliance requirements') that explains what the resource means. It is clear and distinguishes itself from nearby tools like list_device_policies through the specific 'posture rules' terminology, though it does not explicitly name sibling tools.

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 no guidance on when to use this tool versus alternatives such as list_device_policies or list_devices. There is no mention of prerequisites, scope, or context in which device posture rules are relevant, so an agent must infer usage purely from the tool name.

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