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

Annotations already declare idempotentHint=true and destructiveHint=true; the description adds real behavior beyond that — weekly pickup Orders auto-generate on the chosen day until term end, and the re-call no-op semantics. It does not explain why destructiveHint is set (what gets altered/consumed), leaving one gap.

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?

Front-loads the operation and required inputs, then layers precondition, side effect, and idempotency. Dense but every sentence carries a distinct fact; slightly long for a single tool but nothing is pure filler.

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?

Covers precondition, required inputs, cross-tool constraint on pickup day, post-activation side effects, and idempotency — with no output schema present, the description fully explains the observable consequences an agent needs to reason about.

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%, so baseline is 3, but the description adds meaning beyond the schema: the phone is for pickup-day reminders, and the pickup day must match a campus availablePickupDays value (a cross-tool constraint the schema only repeats). Dorm building/room purpose is left to 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+resource ('Activate a paid Semester Pass') and implicitly distinguishes itself from siblings like get_semester_pass and buy_semester_pass by scoping to the activation step. The parenthetical about PENDING_ACTIVATION status further pins down exactly what operation this is.

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?

Clear precondition: 'Only callable on a pass in PENDING_ACTIVATION status (i.e. payment has cleared)', and it routes the pickup day to list_campuses' availablePickupDays. It stops short of explicitly naming the prerequisite sibling (buy_semester_pass) or stating when-not to use it, so no explicit alternative naming.

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