List Image Posts

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context: that all_pages is bounded and every page consumes API quota. It stops short of describing rate limits, auth/account requirements, or result shape.

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?

Three short sentences, front-loaded with the resource and followed by the quota caveat. Nothing is wasted, though the opening sentence duplicates the name rather than spending the space on scope or differentiation.

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 a fully described schema and complete annotations, the description needs only light support, and the quota/bounded-pagination note partially covers that. However, for a paginated listing tool it omits any guidance on filtering scope, defaults, or how to relate it to the sibling list_posts, leaving gaps an agent would have to infer.

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 page, per_page, space_id, account, all_pages and max_items. The description only reinforces all_pages semantics, adding no format or default detail beyond what the schema fields already provide; 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?

"List Image Posts" restates the tool name and title almost verbatim, and "Reads community data" is vague. The verb+resource is clear enough that an agent knows it enumerates image posts, but nothing distinguishes it from siblings like list_posts, list_spaces, or list_live_rooms beyond the noun.

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 or when-not-to-use guidance, and no alternative is named. The note about bounded all_pages hints at a usage mode but never states which conditions should lead an agent to pick this tool over list_posts.

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