get_thread_images

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

Annotations declare readOnlyHint=true, and description adds behavioral details: costs one throttled request per image, token cost (~4.6k per image), default/max for max parameter, and returns summary plus images as blocks. No contradictions.

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 well-structured sentences with every sentence adding value: front-loaded purpose, specific examples, cost info, and parameter guidance. No wasted words.

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?

Given no output schema, description adequately covers return type (summary plus images as blocks), usage context, cost, defaults, and distinguishes from sibling tool get_thread. Complete for a tool with 4 parameters.

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%, baseline 3, but description adds significant context: max parameter has default 4, max 5, and cost details; url parameter suggests origin from search_forum result; page is clamped to lastPage; threadId is an alternative to url.

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?

Description explicitly states the tool downloads image attachments at full size for readability via vision, specifies the context (pricing tables, stock boards, etc.), and distinguishes itself from get_thread which only returns text.

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?

Provides clear guidance on when to use ('much of the vendor pricing is image-only and invisible to get_thread's text') and how to cap downloads with max, but does not explicitly state when not to use or list alternatives besides get_thread.

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