roboshadow_get_device_user_profiles

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 explicitly warns that the data is PII-bearing and admin-gated, which are valuable operational and security traits. The verb 'List' also implies a read-only operation, though it does not mention pagination, rate limits, or failure modes. The added admin/PII context goes beyond a simple tautological statement and is genuinely useful.

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?

Two short sentences. The first states the action, scope, and key output fields; the second adds operational warnings. There is no filler, redundant phrasing, or repetition of schema content. Every element contributes to the agent's understanding of what the tool does and what constraints apply.

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 two-parameter list tool with no output schema, the description sufficiently covers the return contents (SID, disk path) and the key context (single device, PII, admin-gated). It could be more complete by explicitly naming the sibling roboshadow_get_device_users as the alternative for non-Windows or device-level user listings, but the essential context is present.

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%: both deviceId and organisationId already have clear descriptions in the input schema. The tool description adds no extra parameter-level detail or examples, so the baseline of 3 applies. The schema already does the heavy lifting, and the description does not need to compensate.

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'), a clear resource ('Windows user profiles'), and a scoping qualifier ('on one device'), while also naming the output fields (profile SID and disk path). It distinguishes itself from the sibling roboshadow_get_device_users by specifying 'Windows user profiles' rather than just users on a device.

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 indicates the tool targets a single device, which implies when to use it, but it provides no explicit guidance on when to use this tool versus alternatives like roboshadow_get_device_users or roboshadow_list_devices. There are no exclusions or 'use this instead' statements, leaving the agent to infer selection criteria from the tool name and description alone.

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