mdl_custom_lists_featured

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no return shape, pagination behavior, ordering of "featured" results, or scope.

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?

Very short, but this is under-specification rather than earned conciseness — three words that convey almost no actionable information. Brevity here comes at the cost of usefulness, not from trimming waste.

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 read-only, paginated list endpoint with no output schema and 0% parameter documentation, the description should at minimum clarify what "featured" means and how page/limit work. As written, an agent has to guess the ordering and semantics.

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% and the description supplies no meaning for the two pagination parameters (page, limit). The agent gets only names, types, defaults, and bounds, with nothing explaining what they control or how pagination interacts with the featured feed.

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?

"Custom Lists: featured" is a fragment that essentially restates the tool name rather than stating a verb+resource action. It hints at retrieving featured custom lists but offers no verb and no differentiation from siblings like mdl_custom_lists_popular, mdl_custom_lists_trending, or mdl_articles_featured.

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 when-to-use guidance, no mention of alternatives among the many sibling custom-list endpoints (popular, trending, recent_activity, get_user_lists), and no prerequisites or exclusions.

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