search_posts

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

With no annotations, the description carries full burden for behavioral transparency. It only states 'Search Posts' without revealing safety, authentication, rate limits, or what happens (e.g., returns list of posts). Insufficient for a search tool.

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?

Extremely concise but under-specified. The single phrase fails to convey any actionable information, missing a valuable opportunity to describe the tool's functionality.

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?

Lacking any context on output, filtering, or behavior. With no output schema or annotations, the description should compensate but fails to, making it incomplete for an agent to use effectively.

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?

Input schema has zero parameters (100% coverage by default). Baseline is 4, but the description adds no meaning beyond the tool name. It doesn't clarify how the search works without parameters, so by formula it gets 3.

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 'Search Posts' is extremely vague. It doesn't specify the source or scope of posts, nor does it differentiate from sibling tools like 'search_post_by_hashtag' or other search tools, making it hard for an agent to select correctly.

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 usage guidance provided. The description gives no indication of when to use this tool versus alternatives such as search_companies or search_jobs, nor any prerequisites or constraints.

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