threads_search_posts

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

No annotations are present, so the description must provide behavioral context. It mentions the required permission but omits other traits such as rate limits, pagination behavior, or that results are public. The description is too minimal to adequately convey behavioral traits.

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?

Single, concise sentence that front-loads the purpose. No wasted words, but it may be too brief for the tool's complexity. Still, it is efficient and to the point.

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 the tool has 9 parameters (including enums and pagination cursor) and no output schema, the description lacks context about ordering, filtering, pagination, and result structure. It is not complete enough for an agent to understand how to effectively use the 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?

All parameters have schema descriptions (100% coverage), so the description adds no new information beyond 'by keyword or topic tag', which partially explains q and search_mode. 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?

Clearly states the action (search), the resource (public Threads posts), and the method (by keyword or topic tag). Mentions required permission. Distinguishes from sibling tools like threads_get_posts which retrieves specific posts.

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?

Only notes a permission requirement but provides no guidance on when to use this tool vs. alternatives (e.g., threads_get_mentions, threads_get_posts). Does not specify when not to use it.

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