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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that it does not create an account, learner session, purchase, or message, and notes determinism and boundedness—extra behavioral context beyond annotations. No contradiction.

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 short sentences: the first states the core action, the second states side-effect guarantees. Both sentences are purposeful and free of 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?

With an output schema present and parameter enums, the description covers the key side-effect guarantees and determinism. It doesn't explicitly state usage context versus alternatives, but the schema and sibling names provide enough for an agent to invoke it correctly. Slightly incomplete on when to use, so not a 5.

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 0%, and the description provides no parameter-specific detail. While property names like weeks and daysPerWeek are self-explanatory, the description doesn't compensate for the lack of schema descriptions—it doesn't explain how region or course affect the schedule or what 'bounded' means for the numeric fields.

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 'Compute a deterministic, bounded study schedule' with a specific verb and resource, and the title clarifies it's a preview. This distinguishes it from siblings like list_study_options and get_driving_guide, which list or retrieve rather than compute.

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?

No explicit when-to-use or alternative tools are mentioned. The note that the preview is not saved implies use for trial calculations, but this is indirect. The agent is left to infer usage context from the sibling names.

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