bluesky_action

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

With no annotations, the description must disclose behavioral traits like authentication, rate limits, or side effects. It does not mention any, only listing action types. The schema's 'password' field hints at auth, but the description fails to elaborate.

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 sentence, which is concise but under-specified. It lists sub-actions without any structural hints (e.g., prerequisites, ordering), making it less useful despite brevity.

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 9 parameters, no output schema, and diverse sub-actions, the description is vastly incomplete. An agent cannot infer how to use the tool correctly for any specific action without additional information.

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 only 22% (2 of 9 params have descriptions). The description adds no parameter information beyond the schema—it doesn't map actions to required parameters or explain how 'action' determines usage. This fails to compensate for low schema coverage.

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's for 'Perform a Bluesky action' and lists specific sub-actions (post, read feed, reply, etc.), so the agent knows the general domain. However, it doesn't explain what each sub-action does, which is a minor gap since the tool is the only Bluesky tool among siblings.

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 guidance on when to use this tool versus alternatives (none exist) or when to choose each sub-action. The description just lists sub-actions without context, leaving the agent to guess appropriate usage.

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