get_syllabus_index

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

Annotations already cover the read-only, idempotent, open-world, and non-destructive safety profile. The description adds value by clarifying the returned resource is a URL and how it relates to syllabi, but it does not disclose edge cases such as what happens when no index exists for a term or whether the URL is fetched or constructed.

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 just two sentences, front-loads the main operation, and includes only meaningful context. Every sentence earns its place without unnecessary elaboration.

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 simple one-parameter read-only lookup with annotations covering safety, the description is nearly complete: it states what is returned, what it is used for, and how it relates to a direct alternative. The only minor gap is not explicitly describing behavior when no syllabus index is available.

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 single parameter 'termCode' is already fully documented in the schema with a numeric pattern, an example, and a pointer to list_terms for discovery. The description itself adds no parameter-level detail, so the baseline of 3 applies due to high schema coverage.

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 identifies the specific operation: getting the SimpleSyllabus index URL for a term. It also explains the purpose of that URL and distinguishes it from the direct 'syllabus' URL carried by individual sections, so the tool's role is unambiguous.

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 states that the returned index URL is for looking up published syllabi for a term's sections, and notes that individual sections also have a direct 'syllabus' URL. This gives useful context about when this tool is relevant, though it does not explicitly say 'use this when' vs 'use the section URL when'.

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