List Basic Posts

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds useful context about bounded all_pages and API quota consumption, but it does not cover authentication needs, response shape, or pagination edge cases beyond the quota note.

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 short and front-loaded, with the core purpose stated first and the pagination/quota caveat last. Some redundancy exists because 'List Basic Posts' restates the title and 'Reads community data' is generic, but there is no wasted verbosity.

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 10 optional parameters, rich schema descriptions, and annotations covering safety, the description is adequate but sparse. It omits sibling differentiation, usage context, and filtering guidance, though the structured fields compensate for much of that gap.

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 input schema already documents all 10 parameters thoroughly. The description highlights all_pages and quota cost, but this largely repeats the schema's own all_pages and max_items descriptions without adding new semantic detail.

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 clear verb and resource: 'List Basic Posts' and 'Reads community data.' It implies this is a read-only listing tool, but it does not explicitly differentiate from siblings such as list_image_posts or search, so it falls short of a 5.

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 when-to-use guidance, no alternatives named, and no conditions for preferring this tool over related list or search tools. The phrase 'Reads community data' is too vague to function as usage guidance.

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