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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real behavioural context beyond them: result ordering (newest first), a 50-item ceiling, and that calls are free — all of which affect how an agent plans requests.

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?

A single compact sentence with the core action and constraints front-loaded before the filter list; nothing is padded. The standalone 'Free.' fragment is slightly clipped but carries useful cost information, so only minor style loss.

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, so return shape needn't be explained, and the ordering and 50-item cap are stated. The one gap is that the description never says whether more than 50 results are reachable via pagination or a cursor, which an agent would want to know.

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 100%, so every parameter (city, state, topic, country) is already documented with the same GeoNames/ISO 3166 formats the description repeats. The description adds no syntax or combination semantics beyond the schema, so 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?

States a specific verb and resource ('Browse published messages on Yawplet') plus ordering and a hard cap ('newest first, up to 50'), which lets an agent distinguish it from get_post and search_posts by behaviour. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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?

'Free.' and the filter list imply the browsing/feed use case, but there is no explicit when-to-use versus search_posts or get_post, and no stated exclusions or prerequisites. Usage is inferred rather than directed.

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