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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses nothing about whether this is a read operation, what data it returns, rate limits, or authentication requirements. The single word 'Bluesky' offers zero behavioral context.

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 extremely under-specified. A single word is not 'concise' in a meaningful sense; it lacks any informative content. It is similar to the 'Process' example, which warranted a score of 2 for under-specification rather than true conciseness.

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's likely complexity (a scraping tool for a specific platform), the complete absence of description, annotations, and output schema leaves the agent with almost no guidance. The description is wholly inadequate for correct selection and invocation.

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?

The input schema has one required parameter 'handle' with a description 'Bluesky handle', providing 100% schema coverage. The tool description adds no additional parameter meaning, but the schema already fully documents the parameter, so a baseline of 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?

The description is simply 'Bluesky' – a platform name, not a verb or resource. It does not state what the tool does (e.g., 'Scrape Bluesky profile data' or 'Get Bluesky posts'). This fails to distinguish it from the many other scrapecreators_* tools, which have explicit action-oriented names.

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 context is provided. There is no guidance on when to choose this tool over sibling tools like scrapecreators_basic_profile or scrapecreators_posts. It does not mention any exclusions, prerequisites, or alternatives.

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