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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior context by stating the posts are newest first and naming returned fields such as live URL, warnings, claims to confirm, and engagement metrics, but it omits pagination behavior and does not clarify filter semantics; the status list also omits 'approved' from the schema enum.

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?

The description is a single front-loaded sentence with no wasted clauses, beginning with the ordering. The long comma-separated field list is dense, but it remains appropriately sized for the available space.

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, listing returned fields is valuable and partially compensates for that absence. However, for a list tool with filtering and limit parameters, the description does not explain how status filters results, how limit controls pagination, or when the tool should be used, leaving meaningful gaps.

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 only 50%: limit is documented in the schema, while the status enum lacks a description. The description lists some status values but frames them as returned fields rather than explaining that status filters results, omits 'approved', and never mentions limit or pagination, so it does not compensate for the schema gap.

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 implies a listing of posts and states the ordering, but it never explicitly says 'list posts' or defines the scope. It is understandable from the tool name and title, yet the description itself is more about returned fields than the action, and it does not differentiate this tool from siblings such as amplify_edit_post or amplify_schedule_posts.

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 guidance on when to use this tool versus alternatives. The description does not mention sibling tools, prerequisites, or when not to use it, leaving usage to be inferred entirely from the name and context.

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