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

Annotations already establish that this is a safe, idempotent, read-only operation, so the description is not burdened with safety disclosure. It adds useful behavioral context by stating the response includes weekly hours and date overrides, which is valuable because no output schema exists. It does not mention error behavior for missing schedules, keeping it from a 5.

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 with no wasted words. The verb, resource, and returned content are packed efficiently into one line.

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 single-parameter read tool with rich annotations and full schema coverage, the description supplies the key missing output context: what the schedule object contains. It is slightly incomplete because it does not clarify when to use this tool versus the several other schedule-fetching siblings.

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?

There is only one parameter and the schema description coverage is 100%, with the schema explaining that scheduleId comes from list_schedules. The description adds no additional meaning about the parameter, so it meets the baseline for high schema coverage rather than exceeding it.

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?

Uses a specific verb ('Fetch') and resource ('availability schedule') and states what the response contains: weekly hours and date overrides. It implicitly distinguishes itself from list_schedules by saying 'one', but does not explicitly name or differentiate itself from siblings like get_default_schedule or get_schedule_by_user.

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 gives no explicit when-to-use guidance or alternatives. An agent must infer from the parameter name and the schema note that scheduleId comes from list_schedules; the description itself does not say when to choose this over get_default_schedule, get_schedule_by_user, or get_schedule_by_event_slug.

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