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

Annotations already declare readOnlyHint=true, destructiveHint=false, and a closed-world scope, so safety is covered. The description adds nothing beyond that: no mention of pagination behavior, default page size, or how the platform catalog is scoped (locale), which would be useful for a 10-parameter list endpoint.

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 short sentences with the resource identified first and the usage trigger second, so nothing is buried. Slightly weak because the 'clone' clause is misleading rather than additive.

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?

An output schema exists (return values need no explanation) and annotations cover the safety profile, so the essential framing is present. For a listing tool with ten optional filtering/sorting/pagination parameters at 0% schema coverage, however, the description is too thin to tell an agent how to narrow results.

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%, so the description must carry parameter meaning, and it explains none of the ten parameters. It gives no hint that goal_ids, difficulties, duration_in_weeks, workouts_per_week, search_text, sorting, or pagination exist, leaving the agent to infer everything from bare parameter names.

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 (returns/lists) and resource (platform stock programs), and the parenthetical '(publisher programs)' disambiguates the term. It implicitly distinguishes from list_team_programs by qualifying 'platform stock', but never explicitly names the sibling.

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 'Use when the user wants to browse or clone stock programs' clause gives a trigger context, but the cloning reference is ambiguous because clone_stock_programs exists as a separate tool and this one does not perform the clone. No exclusions or explicit alternative routing are provided.

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