get_results

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

Since no annotations are provided, the description carries the full burden. It explains parameter behavior (e.g., partial match, case-insensitive for course_filter), hints at performance implications for include_details, and describes the return format. Missing details on error handling or authentication, but overall adequate.

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 well-organized with a summary line, structured Args section, Returns note, and examples. It is front-loaded with the purpose and each sentence adds value. The examples are slightly repetitive but overall concise.

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?

Given the tool's complexity (4 parameters, no output schema), the description covers parameters, return type, and includes examples. It lacks details on error states or authentication, but for a read-only retrieval tool, it is reasonably complete.

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 compensates fully by explaining each parameter: limit (max results, default 15), offset (skip, default 0), course_filter (partial match, case-insensitive), and include_details (saves API calls if False). This adds significant meaning beyond the schema.

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 'Retrieve student results/grades' and specifies the return type as a dictionary with results and pagination info. However, it does not explicitly distinguish this tool from siblings like get_reports, which may partially overlap in functionality.

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 provides examples and notes that include_details=False saves API calls, giving some usage context. However, it lacks explicit guidance on when to use this tool versus alternatives, and does not state any prerequisites or when not to use it.

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