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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. With no output schema, the description usefully enumerates the per-entry fields returned (original post id, active flag, recycle count, last-recycled time, earning metrics), which is real behavioral context. It stops short of stating ordering, pagination, or freshness guarantees for the recycling schedule.

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?

Four sentences, each carrying distinct load: definition, return fields, use case, and sibling routing. The core identity of the tool is front-loaded before any detail.

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?

There is no output schema, so the description carries the return-value burden and discharges it by naming the fields each entry contains. Combined with the routing to get_post for deeper content, an agent has everything needed to call this and interpret the result.

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?

The tool takes zero parameters, so 4 is the baseline. The mention of passing a postId to get_post is guidance for a different tool rather than a parameter of this one, so it does not add schema-level meaning 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?

States a specific verb and resource ('List the evergreen library') and then defines that resource operationally as 'published posts that performed well and that KreatorMesh re-posts on a schedule.' It explicitly distinguishes itself from the closest sibling by naming list_posts for the unfiltered case, so an agent can route 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?

Gives both a positive trigger ('Good source material when asked what to post next') and two explicit alternatives: get_post for caption/media of a specific entry, list_posts for every post rather than only the library. When-to-use, when-not-to-use, and the routing mechanism are all present.

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