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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful behavioral context: the data reflects what non-logged-in users see, implying public-only visibility, and explains that projection_preset, data_fields, and item_fields support payload reduction. No contradiction with annotations.

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 with no fluff. The core purpose and scope come first, and the brief mention of payload reduction options is framed as a single supporting statement. Every word adds value.

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 read-only, idempotent tool with fully documented parameters and no output schema, the description covers the essentials: what is returned, the visibility scope, and the available payload reduction options. It could add pagination behavior or define what counts as 'media', but these are minor gaps given the annotations.

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 the schema already documents all six parameters. The description's mention of projection_preset, data_fields, and item_fields for 'payload reduction' groups them conceptually but adds no per-parameter meaning beyond the schema, keeping this at the baseline 3.

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 states a specific verb ('Returns') and resource ('public posts from an X community's Media tab'), plus a clear scope ('as visible to not logged in users'). This distinguishes it from sibling tools like x_get_community_posts by narrowing to the Media tab specifically.

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 gives clear context: use this for posts from the community's Media tab, not general posts. However, it does not explicitly name alternatives or state when not to use it versus x_get_community_posts, so it stops short of full exclusionary guidance.

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