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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description usefully adds that native/off-platform posts and media are included, which is real scope information, but says nothing about pagination, ordering, or volume behavior beyond the schema's limit.

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, no redundancy, and the scope statement is front-loaded ahead of the usage rationale. The second clause ('reusing what worked beats starting from zero') leans slightly promotional but still carries actionable intent.

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?

For a low-complexity listing tool with no output schema, the description covers what is returned (published content plus media, including native posts) and when to reach for it. Missing only secondary detail like ordering or pagination, which is minor given zero required params.

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 coverage is 100% and both params (limit, workspaceId) carry their own descriptions, including the workspace/account fallback rule. The description adds no parameter meaning beyond the schema, 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?

The description characterizes the resource well: 'content already published on the networks, INCLUDING posts published natively outside Ignix, with its media,' which conveys the 'reusable library' scope. It implies listing but never states the verb directly, and it does not explicitly contrast with list_posts or list_library_media, so sibling differentiation is left to inference.

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 place to look before writing something new: reusing what worked beats starting from zero' gives a clear when-to-use signal (prior to authoring new content, for reuse). It does not name an alternative tool or state exclusions, so it is context without routing.

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