route_non_priv_comps_dangerous_rights_to_comps

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

No annotations are provided, so the description carries full burden. It hints at high resource usage ('[HIGH RAM]') but does not disclose critical behavioral traits such as whether this is a read-only operation, what 'dangerous rights' entail, potential side effects, or output format. The description is too vague to inform safe or effective use.

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 (one sentence plus a note), which is efficient, but it is under-specified rather than concise. The '[HIGH RAM]' note adds some value, but the core purpose remains unclear, making the brevity more of a deficiency than a strength.

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, 0% schema coverage, no output schema, and a complex tool name implying security analysis, the description is completely inadequate. It fails to explain what the tool does, how to use it, what parameters mean, or what to expect, leaving the agent unable to operate this tool effectively.

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%, and the description does not mention the 'domain' parameter at all. With 1 required parameter undocumented in both schema and description, the agent lacks any semantic understanding of what input is needed or how it affects the tool's behavior.

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 non-privileged computer(s) with dangerous rights to computer(s)' which is a tautology of the tool name, adding only '[HIGH RAM]' as extra information. It does not specify what 'route' means (e.g., find paths, list relationships), nor does it distinguish from siblings like 'route_non_priv_comps_dangerous_rights_to_gpos' or 'route_non_priv_users_dangerous_rights_to_comps'.

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. It does not mention prerequisites, context, or compare to sibling tools, leaving the agent with no basis for selection among similar routing tools in the list.

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