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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds a genuinely new behavioral fact for the agent – that no key or authentication is required – which is not expressed in the structured fields.

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 prose is literary and padded ('an agent's first training outside its lab'), and the single most actionable instruction – read this before licence_start – is placed last rather than front-loaded. The lesson enumeration does carry signal about scope, so it is not pure waste, but the framing sentences do not earn their length.

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?

With no parameters, no output schema, and annotations covering the safety profile, the description only needs to convey what the content is and where it sits in the flow. It does both, listing the lesson scope and pinning the call before licence_start; only the absence of guidance about the related licence_answer step leaves a small gap.

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 tool takes zero parameters and the schema is empty at 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 establishes that this returns curriculum/lesson content for the licence program and names the sibling it precedes ('Read it before licence_start'). The functional verb is never stated cleanly – 'the apprenticeship', 'the ten lessons' describe content rather than the act of retrieving it – but the combination of name, content inventory and ordering against licence_start makes the tool's role discriminable.

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?

It gives an explicit sequencing rule ('Read it before licence_start') and a precondition ('Free, no key'), which tells the agent both when to call it and what is required. It does not say when *not* to use it or how it relates to licence_answer/get_licence, so it stops short of full when/when-not guidance.

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