mdl_custom_lists_trending

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, covering the safety profile. The description adds nothing beyond that: no pagination behavior, no result shape, no rate or scope context. It contributes no behavioral value over the structured fields.

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?

It is short, but this is under-specification rather than effective conciseness — two words that repeat the name without front-loading any actionable information. Nothing in the fragment earns its place.

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 paginated list endpoint with two undocumented parameters and no output schema, the description omits everything an agent needs: what a 'trending' list is, ordering, return contents, and how pagination works. It is not complete enough to call the tool confidently.

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?

Both parameters (page, limit) have 0% schema description coverage, so the description carries the full burden of explaining them and instead says nothing. It neither clarifies pagination semantics nor states defaults or bounds, leaving the agent to guess from the schema titles alone.

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 'Custom Lists: trending.' is essentially a restatement of the tool name (mdl_custom_lists_trending) rather than a stated purpose. It signals a resource area but gives no verb and no indication of what is actually returned or done, so it borders on tautology.

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?

There is no guidance about when to call this versus the many sibling list tools (mdl_custom_lists_popular, mdl_custom_lists_featured, mdl_custom_lists_recent_activity). The agent is left to infer that 'trending' is a distinct ordering, with no exclusions or conditions given.

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