pup_list_plans

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

The readOnlyHint annotation already covers the safety profile, and the description adds that the data is returned as PickUp Patrol provides it. However, it does not disclose ordering, pagination, or potential size/volume behavior beyond the date range.

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 sentence that packs the resource, scope, and data source with no filler. The most important distinction — every student and date range — 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 read-only listing tool with two well-documented parameters, the description provides sufficient scope and a hint at the return style ('as PickUp Patrol returns them'). An output schema is absent, but the description covers the essential invocation context.

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 input schema already fully documents both parameters as YYYY-MM-DD strings. The description only reinforces the date-range concept and does not add extra semantic 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?

The description clearly identifies the verb ('list'), the resource ('plans'), and the scope ('every student on the account, across a date range'). It is distinguishable from singular plan tools like pup_get_plan and from default-plan tools, though it does not explicitly name those alternatives.

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 phrase 'across a date range for every student on the account' gives clear context for when this bulk retrieval tool is appropriate. It does not offer exclusions or point to siblings, but the intended usage is readily inferred.

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