get_posts_by_ids

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

No annotations provided, so description carries full burden. Discloses max 50 posts, returns found posts and not-found IDs. Implies read-only by using 'Retrieve'. Could be more explicit about idempotency or side effects, but adequate.

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, purpose front-loaded, Args section clear. No fluff. Efficient communication.

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 or annotations, description covers key aspects: input, limit, return structure (found posts and not-found IDs). Could mention error handling or order, but sufficient for a simple retrieval tool.

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 0%, so description compensates well. Explains query_id as 'Dataset ID from list_data_queries' and post_ids as 'List of post ID strings to retrieve (max 50)'. Adds meaningful context beyond schema types.

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?

Clearly states the verb 'Retrieve full post details' for a specific resource (list of post IDs by ID). Includes max limit and return format. Distinct from sibling tools like search_posts which are query-based.

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?

Implies usage when you have specific post IDs, but no explicit when-to-use or when-not-to-use compared to alternatives like search_posts. Only constraint is max 50 IDs.

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