alertops_get_oncall_now

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly indicates a read-only, current-state lookup and describes the return content: each group and its current on-call member(s). It does not cover edge cases like empty groups or timezone handling, but for a simple list operation the behavior is adequately transparent.

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?

Two short sentences deliver the core purpose, scope, and return shape without waste. The most important information is front-loaded.

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?

For a tool with one optional parameter, no output schema, and no annotations, the description provides enough to invoke it correctly and understand its return value. It could mention what happens when no one is on-call or how the current moment is interpreted, but these are minor gaps for a simple current-state lookup.

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 100%, and the schema already documents that group_id is optional, limits to a specific group, and references alertops_list_groups. The main description repeats the optional single-group behavior but adds no new meaning 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 uses a specific verb ('List') with a clear resource ('who is on-call right now') and explicitly states the scope: every group or a single group. It also distinguishes the tool from schedule-related siblings by emphasizing 'right now' vs. schedules.

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 gives clear context: omit group_id to see all groups, or provide it to limit to one group, and the schema ties group_id to alertops_list_groups. It does not explicitly name alternative tools or state when not to use this tool, but the intended usage is unambiguous.

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