set_mastery_learner_override

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

Annotations already declare readOnlyHint false and destructiveHint false. The description adds that it 'Changes stored DeepTutor learning data', warns to check target ID and values, and emphasizes the action is a learner declaration, not an inference. This enriches the behavioral context beyond the annotations without 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?

Two sentences, both essential. The warning is front-loaded, and the second sentence defines the exact purpose. Zero fluff, maximum information density.

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 mutating tool with 5 parameters and a confirm flag, the description explains the core purpose and the critical condition. The output schema exists, so return values need not be described. Minor gaps like potential side effects or prerequisites are not covered, but overall it is complete enough for correct invocation.

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%, so all parameters are documented in the schema. The tool description does not add extra meaning beyond the schema; for example, the `confirm` parameter's authorization semantics are already in the schema. Baseline 3 is appropriate.

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 states a specific action: 'Record an explicit learner declaration of mastery or non-mastery', and clearly identifies the resource (DeepTutor learning data). It distinguishes itself from siblings by being the only tool that sets a learner override. The verb 'set' and the explicit scope are unambiguous.

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?

Provides explicit guidance on when to use: 'call only when the learner explicitly requests this action' and 'never infer this from Codex conversation alone'. This is strong usage direction, though it does not name alternative tools. The condition is clear enough for an agent to decide correctly.

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