route_azure_users_with_dangerous_rights_to_users

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

No annotations are provided, so the description carries full burden. It mentions a prerequisite ('azurehound') but lacks details on what the tool does behaviorally (e.g., what 'route' entails, output format, potential side effects, or rate limits). This leaves significant gaps for a tool with no structured safety hints.

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 and front-loaded, but the [WIP] tag and lack of complete sentences reduce professionalism. It's concise but under-specified, not efficiently informative.

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 no annotations, no output schema, and a complex tool name implying security analysis, the description is incomplete. It lacks details on behavior, output, or how it fits with siblings, making it inadequate for safe and effective use by an agent.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate, but it includes a prerequisite note ('azurehound') that provides some operational context beyond the schema.

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 'Route from Azure User principal(s) that have dangerous rights to Azure User and User principal(s)' which provides a basic action and resources, but it's vague about what 'route' means operationally and doesn't distinguish from similar sibling tools like 'route_non_privileged_users_with_dangerous_rights_to_users'. The [WIP] tag further undermines clarity.

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 hints at a prerequisite, but provides no explicit guidance on when to use this tool versus alternatives like other 'route' tools in the sibling list. No context on use cases or exclusions is given.

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