get_grading_guidelines

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

No annotations are provided, so the description carries the full behavioral burden. It says the guidelines are 'saved', implying persistence, but does not state that this is a read-only operation, what happens if the course has no guidelines, or whether permissions are required.

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 a single, tight sentence with no wasted words and is front-loaded with the resource being returned. It is appropriately sized for a simple getter, though the missing verb slightly reduces clarity.

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 getter with no annotations and no output schema, the description states the resource and its scope at a basic level. It does not mention read-only semantics or parameter sourcing, leaving some gaps that the bare schema cannot fill.

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%, so the description must compensate. It implies that the resource is scoped 'for a course', which loosely maps to course_id, but it adds no detail about the expected ID format, where to obtain it, or validation behavior. One required parameter remains essentially undocumented.

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 names the resource (grading guidelines and late-penalty tiers for a course) but uses a noun phrase with no verb, so the retrieval action is only implied by the tool name. It is distinguishable from set_grading_guidelines by the get_ prefix, but the description itself does not state that distinction.

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?

There is no guidance on when to call this tool versus siblings such as list_grading_courses or set_grading_guidelines, and no prerequisites or context conditions are given. The agent must infer usage purely from the name.

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