schoolpass_list_drivers

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds useful context about parent-account scoping and the optional carpools behavior, but it does not disclose response format, pagination, or any access requirements. Given annotation coverage, this is acceptable but not richly 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?

A single, front-loaded sentence that communicates the core purpose immediately and adds the relevant optional detail without wasted words.

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 zero-parameter, read-only list tool, the description is nearly complete. The only minor gap is the unresolved 'optionally including carpools' behavior, since there is no input parameter to control it. Otherwise, an agent can understand what the tool does and when to invoke it.

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 tool has zero parameters, so the schema leaves nothing to explain. The description's mention of 'optionally including the carpools' adds some behavioral context, though it is slightly ambiguous given that no parameter exists to request this option.

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') and identifies a clear resource: authorized pickup drivers registered on the parent account. It also mentions the optional carpools inclusion, which distinguishes this from sibling tools like schoolpass_list_students and schoolpass_list_dismissal_locations.

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: this is for listing authorized pickup drivers on the parent account. It does not explicitly mention alternatives or exclusions, but the resource and purpose are specific enough that an agent can infer when to select it over sibling list tools.

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