LessonTariffsCreate

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

Annotations already signal mutation (readOnlyHint=false), non-idempotency, and non-destructiveness, but the description adds no behavioral context beyond restating the creation intent. It does not disclose, for example, whether duplicate names are allowed, whether bodyDurations is processed atomically, or what side effects occur.

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 states the purpose without filler. It is appropriately concise, though it sacrifices potentially useful behavioral and usage detail.

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 creating operation with a nested bodyDurations structure and no output schema, the definition lacks outcome information, error behavior, and relationship to related tariff operations such as LessonTariffsAddTariffDuration. An agent cannot tell what a successful response looks like or what constraints apply.

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 provides 100% property-level descriptions for bodyName, bodyDurations, and bodyDescription, so the description does not need to compensate. The description adds no additional meaning about valid values or relationships between parameters, which keeps this at the baseline.

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 ('Create') and resource ('new lesson tariff'), making the operation unambiguous. It is easily distinguishable from sibling tools such as LessonTariffsGetList, LessonTariffsDelete, and LessonTariffsAddTariffDuration.

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 LessonTariffsAddTariffDuration or other LessonTariffs operations. There is no mention of prerequisites, exclusions, or use-case context, so an agent must infer the correct selection from the name alone.

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