bluesky_mentions

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

Without annotations, the description partially fills the gap by stating it lists notifications, returns a specific object, and mentions common errors and fallback behavior. However, it does not disclose rate limits, side effects, or confirm read-only nature.

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, using three sentences to cover purpose, defaults, FREE status, required configuration, return format, and errors. It is front-loaded with the main action and avoids unnecessary details.

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 no annotations and no output schema, the description provides a good level of completeness: it states the return structure, common errors, and fallback. It lacks ordering information but covers the essential context for an agent to use the tool correctly.

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?

All three parameters have descriptions in the schema (100% coverage), so baseline is 3. The description adds the default reasons ('mention','reply') and valid values for 'reasons', but does not provide additional meaning for 'limit' or 'cursor' beyond 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 it lists notifications (mentions/replies) for the configured Bluesky account, with optional inclusion of reposts/likes/follows. It distinguishes itself from siblings like bluesky_post, bluesky_reply, and bluesky_search by focusing on the user's own notifications.

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 for checking notifications but does not explicitly provide when-to-use or when-not-to-use guidance relative to sibling tools. It mentions 'FREE' and required credentials, but no alternatives are suggested.

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