search_starter_packs

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds that the tool works without authentication (consistent with openWorldHint) and mentions rate limiting. It also describes the return fields (name, description, creator, member count, joined counts), providing useful context beyond the structured annotations.

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 two sentences, efficiently conveying purpose, behavior, and alternative tool. No redundant text; every phrase adds value.

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 read-only search tool with 3 parameters and an output schema, the description covers the key aspects: authentication, rate limiting, pagination, and return fields. It could explicitly mention that the output is paginated, but the schema already handles that. A high score given the tool's simplicity.

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%, so baseline is 3. The description adds value by explaining that plain keywords work and Lucene query syntax is recommended for advanced queries, and that the default limit is 25. This goes beyond what the schema provides.

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 for Bluesky starter packs by keyword, specifies the API endpoint, and distinguishes it from 'get_starter_pack' for fetching full details. The verb 'search' combined with resource 'starter packs' is specific and unambiguous.

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 provides clear guidance on use cases: use this for keyword search, and direct users to 'get_starter_pack' for full pack details. It also notes that authentication is not required and mentions rate limiting, but does not explicitly state when not to use this tool.

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