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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so a lower burden applies. The description still adds real context beyond them: the auth requirement (Cotlet API key with access to this app) and that results include length in weeks.

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 purpose is front-loaded, but the first sentence restates the title/first clause almost verbatim ("Programs in your Program Library..." then "Lists the programs in your Program Library..."), which is redundant waste in an otherwise short passage.

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, zero-required-param list tool with full schema coverage and safety annotations, the description covers purpose, auth, and return content adequately. Pagination and result-limit behavior are unstated but minor for this simplicity level.

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% (the lone 'search' param already documents 'Program name contains'), so the baseline is 3. The description adds no syntax, matching behavior, or format detail for search, and mentions program_id which is not actually an input parameter here.

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?

Clearly states the verb (lists) and resource (programs in your Program Library) and adds that length in weeks is included. This distinguishes it from everfit_list_workouts, everfit_list_autoflows, and everfit_assign_program, though it does not contrast those siblings 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?

"Pass program_id to assign_program" implies the downstream workflow this list feeds, giving implied usage. However, there is no explicit when-to-use vs. when-not, and no filtering guidance even though a search param exists.

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