banner_get_weekly_schedule

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is fully covered. The description adds useful behavioral context beyond annotations: classes are grouped Monday through Sunday and include time, room, building, section, and courses without scheduled meetings. No contradiction with annotations.

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?

Three purposeful sentences with no filler. The action and resource are front-loaded, output details follow compactly, and the term behavior is stated in one concise sentence. Every clause earns its place.

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 tool with one optional parameter and no output schema, the description is complete. It explains what data is returned, how it is organized, the default term behavior, and the term override. An agent has enough information to select and invoke the tool correctly.

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 the schema already documents the optional term code and its default behavior. The description adds a small nuance by saying 'registered past term,' which clarifies that the term must be one the student is registered in, but it does not substantially elevate meaning 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 states a specific verb and resource: 'Get the student's UPC weekly class schedule from their Banner registrations.' It also describes the returned grouping and fields, making the tool's purpose unmistakable. The explicit 'Banner' source separates it from the sibling campus_get_weekly_schedule.

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 for when to use the optional term parameter: 'Uses the active term by default; pass term to consult a registered past term.' It does not explicitly name alternatives or exclusions, but the Banner-specific scope implies when this tool applies.

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