Get Outcome Results

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

Annotations include readOnlyHint=true and openWorldHint=true, which already signal a safe read operation. The description adds that results are per-student and filterable, but does not disclose pagination behavior, return structure, or any error conditions. With annotations providing the safety profile, a 3 is appropriate.

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, compact sentence that front-loads the core purpose and lists optional filters efficiently. No extraneous words or repetition of schema details; it earns its place.

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?

The tool is relatively simple with good schema coverage and no output schema, but it lacks information about pagination, response format, and authentication. Given the complexity and the presence of sibling outcome tools, the description could be more complete by specifying default behavior (e.g., whether all students are returned unless filtered).

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 100%, and all parameters have descriptions. The tool description adds the context 'per-student' and 'course' but does not clarify parameter usage beyond the schema. The schema already describes filters like user_ids and outcome_ids, so the description contributes limited additional 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 clearly states the verb 'get' and resource 'per-student outcome results' for a course, with optional filters. It distinguishes from siblings like 'get_outcome_rollups' by specifying per-student granularity and mentions filters, but doesn't explicitly compare to rollups.

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 implies use for retrieving outcome results with filters, but does not specify when to use this versus alternatives like 'get_outcome_rollups' or 'get_outcome_contributing_scores'. It provides context for optional filters but no explicit exclusions or alternative recommendations.

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