list_lesson_plans

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, the description itself adds no behavioral context beyond the name—no mention of pagination behavior, default ordering, or what the returned list represents.

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 short, but acceptable conciseness requires a sentence to add information. 'List Lesson Plans' is only three words and repeats the tool name, so it does not earn its place.

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?

Even though an output schema exists and annotations cover safety, the description is too sparse for a tool with five optional filters and many list siblings. It does not explain whether filters are combinable, what the default scope is, or whether the result is limited to the current user’s context.

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 five parameters are documented in the input schema. The description adds nothing to the parameter semantics, but per the rubric the baseline is 3 when the schema carries the full load.

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 'List Lesson Plans' is essentially a tautology of the tool name list_lesson_plans and the annotation title. It states a verb and resource but adds no differentiating detail about what counts as a lesson plan or how this tool differs from the many sibling list_* tools.

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 provided about when to use this tool versus alternatives like list_sessions, list_lesson_participants, or list_homework. The description also fails to mention whether filtering is required or optional in practice.

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