Get learning insights

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

No annotations are present, so the description must disclose behavioral traits. It does not mention that the operation is read-only, safe, or any potential costs, side effects, or authentication needs. The filtering behavior is described, but that is a parameter feature, not a behavioral trait.

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, clear sentence that efficiently conveys the core function and filtering option. No extraneous words, though it could be slightly more structured (e.g., bullet list of returned items).

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 no output schema and simple parameter list, the description adequately outlines the tool's purpose and main parameter. However, it lacks details on return format, pagination, error states, or examples, leaving some gaps for an agent to fully understand behavior.

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?

The input schema has 0% description coverage (only types and a default). The description adds meaning for 'fingerprintKey' by clarifying it filters the results, but 'courseId' is left unexplained (only noted with default 'demo'). This partially compensates for the schema deficiency.

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 'Returns what SCP has learned' and lists concrete examples (lessons, preferences, pricing and pace patterns), making the tool's purpose specific and understandable. However, it does not explicitly distinguish the tool from siblings like get_course_context or explain_action.

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?

No guidance is provided on when to use this tool versus siblings or under what conditions (e.g., prerequisites, limitations). The description only states optional filtering, leaving the agent to infer appropriate usage.

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