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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful return-shape information by listing item fields such as type, dayOffset, time, repeat and payload, but it does not describe missing-id behavior, permissions, or payload structure.

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 two tight sentences with the return shape front-loaded and the update workflow cue second. There is little waste, though a few terms such as 'payload' remain undefined.

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 tool with one required parameter and no output schema, the description gives a reasonable field-level summary and one workflow constraint. It remains incomplete because it omits any explanation of the id parameter and does not clarify error or not-found behavior.

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% for the sole required 'id' parameter, so the description must carry the burden of explaining it. The description never mentions the id parameter, its expected format, or what kind of program identifier it refers to.

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 a specific retrieval action: it returns 'One program with every item' and names the item fields. This distinguishes it adequately from list_programs and mutation siblings, though it does not explicitly say it is fetched by id.

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?

It gives one explicit workflow cue: 'Read this before update_program.' It does not explain when to use list_programs instead, nor does it state any exclusions or prerequisites beyond the read-before-update hint.

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