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

Annotations already declare a safe, idempotent, closed-world read, so the description only needs to add context. 'Featuring now' contributes a useful temporal signal (a current, changing snapshot) and the field list previews the response shape, but there is no mention of result size, ordering, or the language-fallback behavior beyond what the schema states.

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?

One compact sentence with the resource and returned fields front-loaded and no filler. The phrasing 'trends migram is featuring now' is slightly awkward but not wasteful.

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 zero-required-parameter, read-only list tool with annotations covering safety and no output schema, the description supplies the essential missing piece: what each result contains. Only the absence of any routing guidance against its migram siblings keeps it from a 5.

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% and the single 'lang' parameter already documents allowed values, default, and the English fallback. The description adds no additional meaning about language selection, so the baseline 3 applies.

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 names the concrete resource (makeup trends currently featured by migram) and enumerates the returned fields (title, tagline, look description, time label), which distinguishes it from migram_list_notes and migram_get_note. The list verb is only implied by the name rather than stated in the description, so it stops short of a 5.

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 explicit instruction on when to call this versus migram_get_note or migram_list_notes, and no exclusions or prerequisites. Usage is only inferable from the resource noun itself.

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