get_backlog

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

With no annotations provided, the description bears full responsibility for behavioral disclosure, but it only says 'Get incomplete past lectures.' It does not disclose ordering, whether results are limited by default, how 'incomplete' is determined, or any other operational behavior beyond the bare resource.

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 extremely concise and front-loaded, using only a few words to convey the core purpose. No filler exists, though the parenthetical 'backlog' is slightly redundant with the tool name and could have been used to add differentiation instead.

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 the large sibling set with several overlapping backlog tools, the description is not complete enough for an agent to reliably select and invoke this tool correctly. It lacks usage context, sibling differentiation, and behavioral details such as result ordering or default limits.

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 already documents all three parameters with descriptions: limit as 'Max items', chapter as 'Filter by chapter', and subject as 'Filter by subject', so schema coverage is 100%. The description adds no additional meaning beyond what the schema provides, which matches the baseline of 3.

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 clear verb and resource: getting incomplete past lectures, with 'backlog' as a clarifying parenthetical. It distinguishes the tool from schedule-related siblings, but it does not differentiate it from other backlog-specific siblings like get_subject_backlog or get_chapter_backlog, so it stops short of a 5.

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?

No guidance is given about when to choose this tool over the many backlog-related siblings such as get_subject_backlog, get_chapter_backlog, get_backlog_summary, or get_oldest_backlog_lecture. The description implies a generic backlog listing use case but provides no exclusions or alternative routing.

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