Get a user's posts

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

With no annotations, the description must convey behavioral traits, but it only states the basic function. It does not disclose pagination behavior, ordering, error handling, or effects. The description adds no context beyond what the tool's name implies.

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, no-waste sentence that immediately states the tool's purpose. It is appropriately sized for a simple getter tool, with no redundant or filler language.

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?

Despite being a low-complexity tool, the description does not explain how to use cursor/limit for pagination or handle edge cases like invalid actor handles. It also does not mention that omitting actor uses the authenticated user, a key detail present only in the schema. The description is incomplete for a first-time user.

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 33% (actor has a description, but limit and cursor do not). The tool description mentions 'specific account' but says nothing about limit or cursor semantics, failing to compensate for the low coverage. Actor's meaning is clear, but the other parameters remain undocumented.

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 tool gets posts from a specific account's profile feed, using 'Get' as the verb and 'posts' as the resource. It distinguishes from siblings like bluesky_get_post (single post) and bluesky_get_timeline (followed accounts' feed).

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 when you need a specific account's posts ('their profile feed'), which differentiates from timeline/search tools, but it does not explicitly state when to use it versus alternatives. No exclusions or explicit when-not-to-use guidance is provided.

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