Pipepost

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's a read-only fetch operation (implied by 'Fetch'), requires no authentication ('No credentials required'), has no cost implications ('FREE — no credit cost'), and describes the scope of what's returned (parents above, replies below). It doesn't mention rate limits or pagination behavior, but covers the essential safety and scope aspects.

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 perfectly sized at three short sentences, each earning its place: first states the core purpose, second adds important behavioral context (no auth required), third adds cost information. It's front-loaded with the main functionality and wastes no words.

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 read-only fetch tool with no annotations but 100% schema coverage, the description provides good contextual completeness. It covers purpose, authentication requirements, and cost implications. The main gap is the lack of output schema, so the description doesn't explain what format the conversation data returns in, but otherwise addresses the essential context needed for this type of tool.

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 fully documents all three parameters. The description doesn't add any parameter-specific information beyond what's in the schema descriptions. It mentions the concept of 'parents above' and 'replies below' which aligns with the depth and parent_height parameters, but doesn't provide additional semantic context beyond the 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 the specific action ('Fetch the full conversation around a Bluesky post') and distinguishes it from siblings by specifying it retrieves both parent posts above and replies below. It explicitly differentiates from bluesky_post (single post), bluesky_reply (create reply), and bluesky_search (search posts).

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 context about when to use this tool ('to fetch context for a post') and mentions 'No credentials required' and 'FREE — no credit cost' which are helpful usage considerations. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the sibling tools.

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