Pipepost

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

With no annotations, the description carries full burden and adds valuable behavioral context: it discloses that root/parent references are computed automatically (helpful for understanding the tool's logic) and notes it's 'FREE — no credit cost' (important for usage considerations). However, it doesn't mention rate limits, authentication needs, or error handling.

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 front-loaded with the core purpose, followed by key behavioral details and cost information in just two sentences. Every sentence adds value with zero waste, making it highly efficient and well-structured.

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 good purpose and behavioral context but lacks details on return values, error conditions, or authentication requirements. For a mutation tool (reply creation) with 3 parameters, this leaves gaps in completeness.

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 100%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema (e.g., no examples or edge cases for 'thread' vs. 'text'), resulting in the baseline score of 3.

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 verb ('Reply to') and resource ('a Bluesky post'), specifying it handles both single replies and chained threads. It distinguishes from sibling 'bluesky_post' (likely for new posts) but not from 'bluesky_thread' (unclear if that's for viewing vs. creating threads).

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 replying to existing posts (vs. creating new ones with 'bluesky_post'), but doesn't explicitly state when to use this tool over alternatives like 'bluesky_thread' or provide exclusions (e.g., not for editing or deleting replies).

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