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

No annotations are provided, so the description bears full burden. It mentions returning level, completed lessons, and next lesson, and implies state mutation ('Place or resume'), but does not disclose potential side effects, authentication needs, or error behavior. Adequate but not exhaustive.

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 concise sentences with no fluff. The critical ordering instruction 'Call FIRST' is front-loaded, and parameter guidance is efficiently integrated. Every sentence adds value.

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, the description covers return values and key parameter rules. It lacks details on error cases (e.g., unknown email, idempotency), but for a session-start tool, the essentials are present. Sufficient for most use cases.

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 coverage is 100%, but the description adds significant value beyond schema: explains that 'learner' must be an email (stable key), that 'name' is for certificates, and that 'level' can optionally override. This aids correct parameter use.

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 specifies 'Call FIRST. Place or resume a learner: returns their level, completed lessons, and the recommended next lesson.' This clearly identifies the tool as an initialization step for a learner session, with specific verb and resource, and distinguishes it from siblings like 'complete_lesson' or 'course_stats'.

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 states 'Call FIRST,' indicating the tool is the entry point. Provides guidance on passing email as 'learner' and using 'name' for certificate, but does not explicitly list when not to use alternative tools. Still, the ordering is clear.

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