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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and the description adds the useful consequence that the class schedule is unchanged. It does not disclose whether the student is notified, whether the action is reversible, or what happens if the request was already handled — meaningful gaps for a state-changing, externally-visible action.

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 short clause that front-loads the action and states the resulting state. No filler, nothing redundant with the title.

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 two-parameter action with annotations and no output schema, the description covers the essential effect but omits the pending-state prerequisite, the delivery of response_note to the student, and any failure behavior. Adequate to invoke, not complete enough to predict side effects.

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 both requestId and response_note are documented in the schema, including the pointer to list_class_change_requests. The description adds no additional parameter meaning, so the baseline 3 applies.

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 action (declines a request) and its outcome (the class stays where it was), which is exactly what distinguishes it from the paired accept_class_change sibling. It never names that sibling explicitly, so the differentiation is inferred from symmetry rather than stated.

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?

Usage is implied: you reject a pending class change request. There is no explicit statement of when to prefer this over accept_class_change, no precondition that the request must still be pending, and no note about what to do first (list_class_change_requests only appears in the schema, not the description).

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