LessonTariffsGetList

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

The annotations already declare the tool read-only and non-destructive. The description adds useful behavioral context by mentioning pagination and a soft-deleted filter, but it does not clarify the default deleted behavior, pagination defaults, or what the response represents. No contradiction with annotations.

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?

A single front-loaded sentence containing the verb, resource, and two key behavioral qualifiers. There is no filler, repetition, or structural overhead.

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 simple all-optional read operation, the description is adequate to select the tool, and the safety profile is covered by annotations. It is less complete for correct invocation because IsDeleted semantics, Search scope, pagination defaults, and return shape are not described, and there is no output schema to fill those gaps.

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 high, but each parameter description is only a type name repeated, so the schema carries little semantic weight. The tool description adds some meaning by tying pagination to the operation and indicating IsDeleted is the soft-deleted filter, but it leaves Search and the exact pageSkip/pageTake semantics unspecified.

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 specific verb and resource: list lesson tariffs, with pagination and a soft-deleted filter. It is clear enough to identify what the tool does, and the resource noun distinguishes it from sibling tools such as LessonTariffsGetTariffDurationList or LessonPackagesGetList, though it does not explicitly name any sibling.

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?

Usage is implied: use this tool to obtain a paginated list of lesson tariffs, optionally filtering deleted records. However, there is no explicit guidance about when to prefer this over alternatives, such as fetching tariff durations or packages, and no exclusions are stated.

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