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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is fully covered by structured data. The description adds only the 'owned content group' ownership constraint; it says nothing about pagination flow, result volume, or what a page contains beyond what the cursor/limit schema fields state.

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 short sentences with no wasted prose, and the required-scope constraint plus the usage hint are front-loaded. The leading line 'List posts' merely restates the name/title, a small redundancy, but the body is tight.

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 should at least hint at the shape of a returned page, but it never does. Cursor-based pagination is covered by the schema's cursor field, so the only real gap is the return payload, leaving the definition adequate but not complete.

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 limit, cursor, status and contentGroupId are all fully documented in the schema, including pagination mechanics and the status enum semantics. The description adds no parameter detail beyond that, 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?

States a specific verb and resource ('List posts') and scopes it to a required owned content group, which an agent can distinguish from the single-post getPost sibling implied by 'before acting on a specific one'. It never names a sibling explicitly, so differentiation rests on inference rather than direct routing.

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?

'Use this to enumerate posts before acting on a specific one' gives a clear workflow context for when to reach for this tool versus acting on an individual post. It offers no exclusions or named alternatives among the many sibling list tools (listStories, listVideos, listMedia), so it stops short of the top band.

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