LessonTariffsDeleteTariffDuration

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

Annotations already declare destructiveHint=true, but the description goes further by specifying that the operation removes the tariff duration and, notably, requires client-side approval. This adds practical behavioral context beyond the structured hints.

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 brief and front-loaded with the core purpose. The warning is slightly redundant with the tool name and destructiveHint, but it earns its place by adding the client-side approval requirement and emphasizing the destructive nature for an AI agent.

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 straightforward deletion with two fully covered parameters, the description provides the key operational caveats: destructive behavior and client-side approval. No output schema exists, but for this simple operation the description is sufficiently complete.

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 the baseline applies. Both parameters are documented as required integers, but the description does not explain the semantic difference between LessonTariffId and LessonTariffDurationId. Description adds no value here beyond the schema.

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?

Description uses a specific verb ('Delete') and a precise resource ('a tariff duration'), clearly distinguishing this from sibling tools like LessonTariffsDelete (which deletes a tariff as a whole) and LessonTariffsAddTariffDuration (which adds one). The resource name alone disambiguates the operation.

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 explicit guidance on when to use this tool versus alternatives, and no mention of sibling tools such as LessonTariffsGetTariffDurationList for finding the correct duration or LessonTariffsDelete for removing the entire tariff. Usage is only implied by the verb and resource name.

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