search_posts

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the search action and scope; it does not explain the return format, result ordering, pagination, or whether it searches all public posts or a restricted set. This is a significant gap for a read operation with no annotation safety signals.

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?

The description is a single, front-loaded sentence with no wasted words. Every word contributes to conveying the tool's core function, making it appropriately concise and easy to parse.

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 low-complexity search tool with a simple schema, the description is adequate for basic selection and invocation. However, with no output schema and no annotations, an agent is left without information about result shape, ordering, or any search constraints, making it minimally complete rather than fully self-sufficient.

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%, and the query parameter description duplicates the tool description ('keywords, hashtags, or phrases'). The limit parameter has clear schema documentation including default and bounds. The description adds no semantic value beyond what the schema already provides, so the baseline of 3 applies.

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 'Search Bluesky posts by keywords, hashtags, or phrases' clearly identifies the action (search), the resource (Bluesky posts), and the method (keywords, hashtags, phrases). This distinguishes it from siblings like search_users and get_user_feed without needing further explanation.

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?

The description implies usage: use when you need to find posts matching certain terms. However, it does not explicitly say when not to use it or mention alternatives such as search_users for user discovery or get_timeline for a feed, leaving the agent to infer context.

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