set_course_unit_covered

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

Annotations only say the tool is not read-only and not destructive; the description adds that it 'changes stored DeepTutor learning data,' warns to check IDs/values, and requires explicit learner authorization. This materially enriches the safety profile.

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 short sentences, each earning its place: warning, invocation gate, and semantic clarification. Front-loading the warning is appropriate for a state-changing tool.

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?

For a simple four-parameter boolean update with a full input schema and an output schema, the description supplies the missing behavioral and authorization context. No obvious gaps remain.

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 covers 100% of the four parameters with descriptions, so the schema carries the semantic load. The description only adds a caution to check target IDs and values rather than per-parameter 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 names the exact action ('Mark one syllabus unit covered or uncovered') and resource (syllabus unit in a course). It also clarifies the record's meaning ('learner record, not proof of mastery'), which separates it from mastery-related siblings.

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 gates invocation to 'call only when the learner explicitly requests this action,' and warns to verify the target ID and values before calling. This gives a clear when-to-use signal even without naming alternatives.

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