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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is settled. The description adds meaningful context beyond that: the result is scoped to 'the person' (their role, their booking rights), which tells the agent the answer is personalised rather than global config. It does not say what happens for an unknown or unauthorised programme id, which keeps it short of 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 sentence, front-loaded with the core purpose before the enumeration. The long parenthetical list is dense but every item carries information the agent cannot get elsewhere (no output schema), so little is wasted; only the phrasing could be tightened.

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?

With no output schema, the description carries the burden of saying what comes back, and the enumeration does that well. Remaining gaps are minor: error behaviour for an invalid programme id and whether it reflects only the caller's perspective are not stated.

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 coverage is 100% and the single parameter is fully documented in the schema as 'Id or domain of one of the person's programmes'. The description reinforces that the programme must belong to the person, but adds no format or resolution detail beyond the schema; 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 and resource ('Explains how one programme works for the person') and then enumerates the exact facets covered: role, matching model, booking rights, limits, goals, terminology, time zone. The singular 'one programme' plus the personalised framing clearly separates it from list-oriented siblings like list_my_programs.

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?

No explicit when-to-use, when-not, or named alternative appears. The enumerated content implies the use case (checking rules/limits before booking or matching), but the agent must infer that from the field list rather than from stated guidance.

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