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

readOnlyHint already declares the safety profile, so the description's added value is the disclosure of what the response contains (games, events, date notes) and the underlying endpoint, which tells the agent this is a single public GET against a specific program. It doesn't cover response size, pagination, or error behavior, keeping it below 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?

Two sentences, zero waste: the payload description leads, the endpoint reference trails. Nothing is repeated from the title or 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?

Given no output schema, the description usefully enumerates the constituents of the schedule, which is the main completeness gap this tool could have had. Missing only peripheral details like response shape or whether date notes are optional.

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?

With one parameter at 100% schema coverage, the schema already documents program_id fully (including the numeric pattern). The description adds nothing about the id beyond the implied scoping, so the baseline 3 applies.

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?

States a specific verb+resource ('The full schedule of a program') and enumerates the returned content (games with teams, times, locations, scores, plus events and date notes), which clearly separates it from list_program_teams and get_program. It stops short of naming those siblings, so differentiation is implicit rather than explicit.

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?

Usage is only implied — an agent can infer this is the tool for retrieving a single program's schedule, but there is no stated when-to-use/when-not or pointer to an alternative for team-level or program-level lookups.

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