get_learner_progress

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

No annotations are provided, so the description must carry the full burden. It discloses the authentication requirement but does not mention whether the operation is read-only, any side effects, rate limits, or the format of returned data. This is adequate but leaves some behavioral details unspecified.

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 description is a single sentence that efficiently conveys the purpose and a key requirement (authentication). No unnecessary information, front-loaded with the primary action.

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 inputs and no output schema, the description covers the essential: what it does and the authentication prerequisite. It could be more complete by hinting at what the progress data includes, but for a straightforward retrieval tool, it is sufficient.

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 has no parameters, so schema coverage is 100%. The description correctly does not add parameter information because none exist. Baseline score of 4 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?

Description clearly states the purpose: 'Get your learning progress from Kadmia'. This is a specific verb ('Get') and resource ('learning progress'), and it distinguishes from sibling tools (bookmark, explain, generate) by focusing on retrieval of progress.

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 states the authentication requirement via KADMIA_LEARNER_ID env var, providing clear context for when to use this tool. It does not explicitly state when not to use it or offer alternatives, but the sibling tools cover other actions, so usage is well-understood.

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