get_cached_course

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

Discloses that the output contains a 'spec_json' field with the full create_full_course spec reusable for re-upload, indicating the result is a read operation with actionable data. No annotations provided, but description covers key behavioral aspect.

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?

Three sentences: first states purpose, second adds output detail, third clarifies parameter. No extraneous words, front-loaded with essential info.

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 retrieval tool with one parameter and an output schema, the description covers the tool's purpose, key output field, and parameter source. Sufficient for correct invocation.

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?

With 0% schema description coverage, the description fully defines the parameter 'course_id' as 'The cache ID (from list_cached_courses)', adding source and purpose beyond the schema type integer.

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?

Clearly states 'Get full details of a cached course, including its JSON spec', with a specific verb and resource. Distinguishes from sibling 'list_cached_courses' which lists but doesn't provide details.

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?

Explicitly says 'course_id: The cache ID (from list_cached_courses)', guiding the agent to use the output of the sibling tool. No explicit when-not-to-use, but context is clear.

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