Get Outcome Rollup

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the 'Read-only' sentence largely restates them. The description does add useful scope context (one score per outcome, per user), but says nothing about ordering, empty-result behavior, or what a missing outcome yields, so it stays at an adequate level.

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 tight sentences with the aggregate-and-scope point front-loaded and the sibling pointer second. No filler or 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?

A simple single-param read tool with rich annotations and a fully documented schema needs little more; the description covers purpose and the key alternative. The absence of an output schema leaves return-shape slightly unspecified, but that is minor for a rollup endpoint.

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?

Only one parameter, course_id, and the schema documents it fully at 100% coverage, including its format and where to obtain it (list_courses). The description adds no param semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb (Get) and resource (rolled-up mastery score per learning outcome) scoped to the calling user in a course. This distinguishes it clearly from get_my_outcome_results, the sibling that returns the underlying individual results.

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 names get_my_outcome_results as the alternative for the individual results behind each score, giving a clear selection rule. An agent knows exactly when to use this aggregate view versus the detailed one.

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