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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The only added value is describing the returned content, which is useful but is a return-shape disclosure rather than behavioral context such as error conditions or behavior when the schedule has never started.

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?

One front-loaded sentence with no filler. Every clause earns its place by naming a field the caller will receive, which is valuable given there is no output schema.

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 read-only single-record fetch with one fully documented parameter, the description covers the important gap left by the absence of an output schema by listing the return fields. What remains missing is minor: behavior for a non-existent id or a schedule that has never run.

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 a single required parameter and schema description coverage is 100%; the schema already explains that id is the sch_… value from create_schedule or list_schedules. The description adds no further semantics about the id, so the baseline of 3 is appropriate.

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 uses a specific verb (Read) and resource (a schedule) and enumerates exactly what the response contains: timetable, time zone, input, cost cap, enabled flag, next start, and last start outcome. This clearly distinguishes it from mutation siblings like update_schedule or delete_schedule, though it never names another tool explicitly.

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 singular 'Read a schedule' implies fetching one record by id rather than listing, which loosely separates it from list_schedules. However, the description gives no explicit when-to-use guidance, no mention of how to obtain the id, and no exclusions relative to get_run or preview_schedule; that information only appears inside the schema's id description.

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