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

Annotations already declare readOnlyHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it states the result ordering (newest first) and what each result carries (location, engagement counts, original post link), plus its use as a post-publish verification step. Only pagination/result-count behavior is left unstated.

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?

Two sentences with zero filler: the first establishes the resource, scope, ordering, and returned fields; the second gives the use cases. Front-loaded and appropriately sized for a simple list tool.

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?

With no output schema, the description usefully compensates by naming the fields in each returned post and the sort order, and the annotations cover safety. It stops short of stating whether paging metadata or a total count is returned, which is a minor gap for a tool that supports offset pagination.

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%, and both parameters (limit, offset) already carry descriptions, bounds, and defaults, so the schema does the heavy lifting. The description says nothing about limit/offset semantics, which is acceptable at full coverage but adds no value here.

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 a specific verb and resource (list posts published by the connected account on PowPow) and scopes it to the caller's own posts in reverse-chronological order. It also enumerates returned fields (location, like/comment counts, original post link), which separates it from search_posts or get_post_detail without opening either schema.

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?

Two concrete use cases are given: retrospective queries ('what have I posted', 'show me my last travelogue') and post-publish verification that a post went live. That is clear positive guidance, but no sibling is named as the alternative for the neighbouring cases (browsing other users' posts, reading replies), so the exclusion boundary is left implicit.

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