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

Annotations already establish read-only, idempotent, and non-destructive behavior. The description adds useful context beyond them: results are newest-first, include status, time, permalink, failure reason, follow-up text, handoffNotes, and statusHint, and the call is FREE. It still omits pagination/default limit behavior.

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?

Front-loads the resource and return shape, then filter options and cost. It is dense but mostly earns its space; the parenthetical status list is somewhat duplicative of the schema enum, though it adds categorization.

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 does a good job naming returned fields and ordering. It is less complete on limit/pagination behavior and does not fully explain all status values, but for a simple read-only list it is largely sufficient.

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 0%, so the description must document all three parameters. It explains status and channelId as filters but never mentions the limit parameter or its default/max, and its status examples omit enum values such as missed, needs_review, cancelled, and posted_manually.

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: lists the user's Instagram/Threads posts booked through AIGE, newest first, with status/time/permalink/failure fields. It distinguishes this from antix_get_post by describing a collection and referencing shared fields, but it does not explicitly distinguish it from other list/history siblings.

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?

The description implies usage by explaining that results can be filtered by status or channelId and are read-only/free. However, it gives no explicit when-to-use/when-not guidance or alternatives such as antix_get_history.

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