find_owned_users_with_azure_tenancy_access

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

With no annotations provided, the description carries full burden. It mentions a prerequisite ('azurehound') which is useful, but doesn't disclose whether this is a read-only operation, what 'owned' means operationally, what format results return, or any rate limits/authentication needs. For a tool that appears to query security data, this is inadequate behavioral disclosure.

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 brief (two short phrases) but contains unnecessary elements like '[WIP]' which doesn't help the agent. The information is front-loaded with the core purpose, but the structure could be cleaner without the work-in-progress tag.

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 1 parameter with 0% schema coverage, no annotations, no output schema, and the complexity of security/privileged access queries, the description is incomplete. It mentions a prerequisite but doesn't explain the tool's behavior, parameter usage, or result format. The [WIP] tag explicitly signals incompleteness.

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 single 'domain' parameter is undocumented in the schema. The description provides no information about this parameter - what domain means, format examples, or constraints. The description fails to compensate for the complete 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 states 'Find all owned user with privileged access to Azure Tenancy' which provides a verb ('Find') and resource ('owned user with privileged access to Azure Tenancy'), but it's somewhat vague about what 'owned' means and doesn't clearly differentiate from sibling tools like 'list_principals_with_azure_tenancy_access' or 'find_owned_users_with_group_granted_azure_access'. The [WIP] tag indicates it's incomplete.

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 includes 'Required: azurehound' which provides a prerequisite, but offers no guidance on when to use this tool versus alternatives like 'list_principals_with_azure_tenancy_access' or 'find_owned_users_with_group_granted_azure_access'. There's no explicit when/when-not usage context.

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