get_on_call_now

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it returns current roster members for rotations, but does not disclose behaviors like timezone handling, empty-result behavior, or whether multiple rotations are aggregated. This is adequate but not rich.

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 concise sentences with no filler. The core action and expected result are front-loaded, and every word adds value.

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 simple, single-parameter, read-only tool with full schema coverage, the description is sufficient to understand what the tool does and what it returns. The lack of an output schema means the exact return structure is not specified, but the description's statement about roster members is reasonably complete for invocation.

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 single parameter 'group' is fully described in the schema as 'Group name or sys_id', and the description adds no additional semantic detail beyond mentioning 'group'. With 100% schema coverage, the baseline of 3 is appropriate.

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 ('Find') and resource ('who is on call for a group right now'), and clarifies the result ('current roster members for the group's rotations'). This clearly distinguishes it from sibling tools like list_rotas, which list schedules rather than current on-call members.

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 implies usage for checking current on-call status but gives no explicit guidance on when to choose this tool over siblings like list_rotas, create_rota_schedule, or create_on_call_override. No alternatives or exclusions are mentioned.

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