get_keyword_search_posts

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

With no annotations, the description carries the full burden. It discloses an important behavioral trait: oversized responses are truncated (truncated: true) and recommends platform filtering for full data. This goes beyond the schema, though it does not cover auth or rate limits. Given the truncation is critical for downstream handling, this is strong transparency.

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 concise sentences: the first states the tool's core function, the second adds a crucial warning about truncation and mitigation. No filler, all information earns its place.

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 simple two-parameter retrieval tool with a complete schema, the description fully covers what the tool does and a key caveat (truncation). No output schema exists, but the return value ('actual social media posts') is clearly stated. The truncation warning and platform-filter tip complete the picture.

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%: both search_id and platform are documented with descriptions, and platform has an enum. The description indirectly references the platform parameter ('request one platform at a time') but adds no new semantic detail beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb (Get) and resource (raw posts from a keyword search), clearly differentiating from sibling tools like get_keyword_search (likely metadata) and get_user_search_posts. It explicitly states it returns actual social media posts matching the search query.

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 usage context: to fetch raw post data. Includes actionable guidance for handling truncation by requesting one platform at a time. However, it does not explicitly mention alternatives (e.g., when to use get_keyword_search instead), but the context is sufficient for a typical retrieval tool.

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