ScheduleCreateLesson

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

The description goes beyond the annotations by disclosing a meaningful side effect: 'Creating a lesson may activate the pupil as a side effect (response includes isActivatedPupil).' This adds behavioral context that readOnlyHint=false alone does not convey. No contradiction with annotations exists.

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 concise and front-loaded: the primary action appears first, followed by two targeted nuances. Every sentence earns its place, with no redundant or filler content.

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?

Given the rich 100% schema coverage and the description's side-effect disclosure, the tool is well specified for selection and invocation. The lack of an output schema is partially compensated by mentioning isActivatedPupil in the response, though full return-value details and any auth/prerequisite constraints are not described.

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 is 3. The description adds genuine value by clarifying that groupId 'accepts the id of any class (group or individual),' which is not fully evident from the schema's generic 'Идентификатор группы.' This helps an agent supply the correct parameter value.

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 clearly states the operation: 'Create a new lesson in the schedule,' with a specific verb and resource. It does not explicitly contrast with sibling tools like ScheduleDeleteLesson or the various ScheduleGet functions, but the create action and schedule domain make the purpose immediately identifiable.

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?

The description implies when to use this tool: when creating a new lesson in the schedule. However, it does not provide explicit when-to-use vs. alternative guidance, nor does it mention any exclusions or prerequisites. The groupId clarification is useful but is parameter guidance rather than usage direction.

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