get_quiz

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavioral detail beyond those annotations: it discloses the kind of settings returned, explicitly states that questions are NOT returned, and calls out the required OAuth scope. This is strong transparency for a simple read operation.

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?

Four short, purposeful sentences with the core action and object first, followed by what is returned, what is not returned, and the auth requirement. Every sentence earns its place and there is no noise or repetition.

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 one-parameter read-only fetch with an output schema and strong annotations, the description is complete: it identifies the resource, the parameter semantics, the scope of returned data, the available alternative for questions, and the required permission. No further information is needed 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?

Schema coverage is 0% and all the schema says is that `id` is a required string. The description compensates well by identifying `id` as the Skilljar id and emphasizing it fetches one quiz. It does not go further, but for a single already-typed parameter this is sufficient added meaning.

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 exact action ('Fetch one quiz by its Skilljar id') and the resource, and explicitly distinguishes the richer settings payload from `list_quizzes`. It also clarifies that questions are excluded, routing an agent away from a natural conflation with `get_question` or `list_questions`.

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?

It explicitly states when to use this tool versus `list_quizzes` (which returns quiz lists but not scoring/presentation settings) and when to use `list_questions` with `filter_quiz_id` for questions. It also names the required OAuth scope, which is directly actionable guidance.

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