LessonTariffsGetTariffDurationList

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

Annotations already establish readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safe-read profile is covered. The description adds the pagination behavior, which is useful, but it does not explain defaults, ordering, or how LessonTariffIds affects the result set.

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?

Six words with no filler, and the pagination qualifier is parenthesized. Every word earns its place; it is appropriately sized for the information it carries.

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?

For a no-required-parameter, read-only list endpoint, the description is nearly sufficient, but with no output schema it leaves return shape, default page size, and the semantics of LessonTariffIds unstated. An agent could invoke it, but would have to infer those details.

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%, earning the baseline 3. The schema descriptions themselves are tautological ('integer (optional)'), and the tool description adds no filtering or pagination semantics beyond the parameter names.

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?

States a specific verb and resource ('List ... lesson tariff durations') and signals pagination. It does not, however, distinguish itself from the sibling LessonTariffsGetTariffForDurationId or LessonTariffsGetList, so it is clear but not differentiated.

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 on when to choose this over LessonTariffsGetTariffForDurationId, LessonTariffsGetList, or related tariff-duration endpoints. The only context is the parenthetical 'paginated,' which implies list use but offers no exclusions or alternative conditions.

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