mdl_articles_featured

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds nothing beyond that – no ordering, pagination behavior, or freshness of 'featured' content.

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 conciseness. Nothing is front-loaded because nothing substantive is stated at all.

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 paged list endpoint with no output schema, the description should at minimum indicate what a page contains and how results are ordered. Nothing beyond the name is conveyed, leaving the agent to guess.

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?

One parameter (page) with 0% schema description coverage, and the description says nothing about it. The agent must infer that page is a pagination index with no stated page size, bounds behavior, or ordering.

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 is a noun phrase fragment, 'Articles: featured.', with no verb to indicate the operation. It implies a listing of featured articles and faintly distinguishes from the sibling mdl_articles_get, but an agent cannot confirm whether this fetches, lists, or filters.

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 on when to use this tool versus mdl_articles_get or any of the many other listing tools. No prerequisites, no exclusions, no alternative named.

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