get_post

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

With no annotations provided, the description carries the full behavioral burden. It correctly signals a read-only retrieval operation via 'Get', but does not disclose potential error conditions, authentication requirements, rate limits, or the structure of the returned post. It is honest but minimal.

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, front-loaded sentence with no filler words. Every word earns its place, and the essential information (what and how) is immediately visible.

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 one-parameter read-only tool, the description provides the core information needed to call it correctly. The absence of an output schema is offset by the straightforward meaning of 'get a post,' though details about return format or error behavior would make it fully complete.

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 schema fully documents the only parameter, 'uri', including its type and description. The description's phrase 'by AT URI' simply echoes the schema without adding extra semantic detail, so the baseline of 3 applies.

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 action ('Get'), the resource ('a specific Bluesky post'), and the required identifier ('by AT URI'). This unambiguously distinguishes it from sibling tools like search_posts or get_user_feed, which operate on queries or feeds rather than a single post.

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 phrase 'by AT URI' implies the intended use case: call this tool when you already have a post's AT URI and want that specific post. However, there is no explicit when-not-to-use guidance or comparison to alternatives like get_thread, leaving some inference to the agent.

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