list_non_managed_service_accounts

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

No annotations are provided, so the description must fully disclose behavior. It only states the action 'List' without details on permissions, rate limits, output format, or whether it's read-only or destructive. This leaves critical behavioral traits unspecified.

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 that is front-loaded with the core action. However, it is overly terse, lacking necessary details, which reduces its effectiveness despite efficient wording.

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?

Given the complexity implied by sibling tools (e.g., security-focused listings), no annotations, no output schema, and 0% schema coverage, the description is severely incomplete. It does not address what 'non-managed service accounts' are, the listing scope, or any behavioral context needed for effective use.

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?

The schema has 1 parameter with 0% description coverage, and the tool description adds no information about the 'domain' parameter. It does not explain what 'domain' refers to, its format, or how it affects the listing, failing to compensate for the lack of schema documentation.

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 'List non-managed service account(s)' restates the tool name with minimal elaboration, making it tautological. It specifies the verb 'List' and resource 'non-managed service account(s)', but lacks detail on scope or output format, and does not differentiate from sibling tools like 'list_enabled_users' or 'list_all_users_with_description_field'.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions, leaving the agent with no usage instructions. Sibling tools include many list operations, but this tool offers no differentiation.

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