delete_schedule

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

Without annotations, the description takes on the full burden and does well by stating the authentication requirement and the permanent nature of the deletion. It does not mention rate limits or other behaviors, but for a simple delete operation, this is sufficient.

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?

Two sentences with no unnecessary words. The first sentence clearly states the action and requirements; the second provides critical usage guidance. Perfectly sized and 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?

Given the tool's simplicity and the presence of an output schema, the description covers the essential context: authentication, permanence, and the prerequisite step. It is complete for a delete operation.

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 schema has one integer parameter (schedule_id) with 0% description coverage. The description adds value by explaining that the id is obtained via list_schedules, but it does not provide additional details about the range or format of the id.

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 action (delete) and the resource (a saved Penn Course Plan schedule), along with the condition (by id, requires auth). It effectively distinguishes from siblings by explicitly mentioning using ``list_schedules`` to find the id.

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 provides explicit guidance: use ``list_schedules`` to find the id before deleting, and warns that the deletion is permanent. This gives clear context for when to use the tool and what to expect.

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