search_bsky_api

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

No annotations are provided, so the description carries the burden. It indicates a search operation (implying read-only) and specifies the content scope, but does not disclose potential rate limits, authentication requirements, or result behavior. For a search tool with no side effects, this is adequate but not rich.

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 concise and front-loaded with the purpose. The args section is clearly formatted and the examples are useful. It could be slightly more structured (e.g., bullet points) but remains readable and focused.

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 2-parameter search tool with an output schema, the description covers the essential usage and parameter details. It lacks explicit references to sibling tools or limitations, but is otherwise complete for its complexity level.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters: query includes multiple examples, and limit specifies a valid range (1-20) and default (10). This adds significant meaning beyond the bare schema.

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 tool searches Bluesky developer API documentation, specifying the resource (docs.bsky.app) and scope (guides, tutorials, advanced topics). It distinguishes itself from siblings by focusing on Bluesky-specific features, but does not explicitly name alternative tools like search_atproto_docs.

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?

It explicitly states 'Use this for questions about Bluesky-specific features like the firehose, federation, moderation, or API usage patterns', giving clear contextual guidance. However, it does not provide when-not-to-use instructions or mention alternative tools for other types of queries.

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