Get On Call Role

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description adds no behavioral context beyond them — no error/not-found behavior, no note about the open-world lookup, nothing about what makes this call fail. With annotations carrying the safety profile the bar is lower, but there is essentially no added information.

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?

A single short sentence with the key qualifier ('by id') front-loaded and zero filler. It is a bit terse rather than padded, so the only knock is that the brevity borders on under-specification.

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 one-parameter read tool with full schema coverage, an output schema, and annotations covering safety, this is nearly sufficient — an agent knows exactly what to pass and what to expect. The missing piece is failure semantics (what happens if the id doesn't exist), which is minor here.

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% and the schema itself explains that `id` fills the /v1/on_call_roles/{id} path and even warns there is no `on_call_role_id` argument. The description contributes nothing beyond 'by id', so the baseline 3 applies.

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?

States a specific verb ('Retrieves') and resource ('On-Call Role') scoped by 'by id', which implicitly distinguishes it from the sibling list_on_call_roles. It does not explicitly name the list/update siblings, so differentiation is inferred rather than stated.

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?

Usage is only implied: you must already have an id, which suggests it follows a list call, but no sibling (list_on_call_roles, update_on_call_role) is named and there are no exclusions or prerequisites. Adequate for a trivial getter, but it offers no routing guidance.

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