aeroedu_kg_record_visit

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

Annotations indicate readOnlyHint=false, and the description confirms it updates mastery score, which is consistent. It adds that the tool should be used after a lesson, but no additional side effects are needed. No contradiction.

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?

Three sentences in Vietnamese, clear and front-loaded: first sentence states main purpose, second adds detail, third gives usage context. No unnecessary words.

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 description fully explains the tool's purpose, when to use it, and parameter details. With 100% schema coverage and no output schema needed, the description is complete for an agent to select and invoke correctly.

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?

All 4 parameters have schema descriptions (100% coverage). The description adds context that mastery_score can be automatically calculated from quiz if omitted, and source defaults to ai_tutor, going beyond 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 the verb 'ghi nhận' (record) and the resource 'node trong Knowledge Graph' and updates mastery score. It distinguishes from sibling tools like kg_node_detail (view) and kg_search (search).

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 explicitly says 'Dùng sau khi HS hoàn thành bài học liên quan đến khái niệm đó' (Use after the student completes a lesson), providing clear context for when to use. It doesn't specify alternatives but sibling tools are distinct.

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