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

readOnlyHint=true already tells the agent this is a safe read. The description adds the underlying endpoint (GET /v1/on-call-override/search/list), which corroborates the read-only nature and hints the backend is a search rather than a full enumeration, but it says nothing about pagination limits or result ordering.

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, with the purpose statement front-loaded and the API reference trailing as secondary detail. Nothing is padded, though the raw endpoint adds little for an agent that only needs to call the tool.

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 three-parameter read tool with full schema coverage and no output schema, the description is serviceable but thin. It never indicates what an override record contains or how many come back by default, which is the main gap given no output schema exists.

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%, so limit, offset, and userId are fully documented in the schema, making 3 the baseline. The description reinforces the userId scoping ('for a given user') but adds no format, default, or boundary detail 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?

States a specific verb and resource: 'Search/list on-call overrides for a given user.' This clearly distinguishes it from the sibling allquiet_create_on_call_override and from allquiet_list_incidents/teams/users. It stops short of explicitly naming how it differs from near-neighbors like allquiet_who_is_on_call.

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 when-to-use or when-not-to-use guidance is given. The phrase 'for a given user' implies the tool is scoped to a single user's overrides, but with siblings such as allquiet_who_is_on_call and allquiet_on_call_report available, no condition is offered for choosing among them.

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