save_schedule

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

With no annotations provided, the description fully discloses that the tool writes to the live Penn account and requires authentication. It explains overwrite behavior and the effect of saving, providing necessary safety information for an agent.

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?

The description is concise at three sentences, front-loading the purpose and key details. Every sentence adds value without redundancy.

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 save tool with 4 parameters and no annotations, the coverage is solid: main behavior, authentication, and overwrite logic are explained. The omission of the 'semester' parameter is a minor gap, but an output schema exists to cover return values.

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 has 0% description coverage. The description adds meaning for 'name' (schedule name), 'sections' (full section IDs), and 'schedule_id' (for overwriting), but fails to explain the 'semester' parameter. This partial compensation yields a mid-range score.

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 states the tool saves a schedule to a Penn Course Plan account so it appears on the website. It specifies the verb 'save' and the resource 'schedule to account', distinguishing it from sibling tools like search_courses or delete_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 explains the tool is for creating a new schedule by name and sections, or overwriting an existing schedule via schedule_id. It also notes the requirement for a session cookie. However, it does not explicitly mention when not to use this tool or alternatives, but the context is clear enough.

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