getBulkPosts

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

With no annotations provided, the description carries full burden but only states the basic retrieval functionality. It doesn't disclose whether this is a read-only operation (implied but not stated), rate limits, authentication requirements, error behavior for invalid IDs, or response format details. Significant behavioral gaps remain.

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?

Perfectly concise single sentence that immediately communicates the core functionality. No wasted words or unnecessary elaboration. Front-loaded with the essential information.

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 7-parameter retrieval tool with no annotations and no output schema, the description is minimally adequate. It covers the primary use case but lacks important context about behavior, alternatives, and response format. The high schema coverage helps, but more behavioral disclosure would be needed for full completeness.

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%, providing complete parameter documentation. The description adds minimal value beyond the schema, only mentioning the 'ids' parameter constraint ('up to 100'). No additional semantic context is provided for the six expansion/field parameters.

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 clearly states the action ('Retrieve') and resource ('posts by their IDs') with a specific scope ('up to 100'). It distinguishes from getSinglePost by handling multiple IDs, but doesn't explicitly differentiate from other bulk operations like searchAll or searchRecent.

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?

No guidance on when to use this tool versus alternatives like getSinglePost (for one ID), searchAll/searchRecent (for query-based retrieval), or getUserTimeline (for user-specific posts). The description implies usage when you have specific post IDs, but provides no explicit context or exclusions.

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