ninja_query_logged_on_users

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

With no annotations, the description must disclose behavioral traits but only states the core function. It does not mention permissions, resource consumption, rate limits, or return format. The agent learns nothing about side effects or operational constraints.

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, clear sentence with no superfluous words. While very brief, it conveys the core purpose without waste. It earns a 4 for efficiency, though it could benefit from slightly more context without losing conciseness.

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?

The tool has three parameters but no output schema, and no behavioral context is added. The description fails to explain what the response looks like, pagination handling, or filter usage. Given the complexity of a query tool across many devices, this is incomplete.

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 coverage is 100%, so the schema already documents all parameters. The description adds no extra meaning beyond the schema, providing no explanation of filter syntax or pagination behavior. Baseline 3 is appropriate as the description does not worsen understanding but also does not enhance it.

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 specifies querying 'the last logged-on user across all managed devices.' The verb 'Query' plus resource 'last logged-on user' is specific, and the phrase 'across all managed devices' distinguishes it from the sibling tool 'ninja_get_device_last_logged_on_user' which targets a single 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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or the fact that a sibling tool exists for single-device queries. The agent receives no help in deciding between this and similar tools.

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