get_schedule

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't state whether this requires authentication, what format the schedule takes, whether it's read-only, or any other behavioral traits. Only the parameter format is mentioned.

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 very short and front-loaded with the purpose, followed by a clear parameter format instruction. It's efficient with no unnecessary words, though it could benefit from more context.

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 tool has one required parameter, no annotations, and a sibling tool (get_attendance) that might overlap, the description is incomplete. It doesn't explain what the schedule contains, whether it's for a user, classroom, or other entity, or how it differs from get_attendance. An output schema exists, so return values needn't be explained, but the context is still insufficient.

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 0%, so the description must compensate. It provides the date format (YYYY-MM-DD) and an example, which adds meaning beyond the schema's bare 'string' type. However, with only one parameter and minimal context, this is a baseline 3.

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 it returns a schedule for a given date ("Расписание на указанную дату"), which is a specific verb+resource. However, it doesn't distinguish itself from siblings like get_attendance, which could also relate to schedules. The purpose is clear but lacks differentiation.

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?

There is no guidance on when to use this tool versus alternatives. No context about when this is appropriate, any prerequisites, or how it relates to get_attendance. The description only restates what the tool does.

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