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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: result ordering (newest first), the engagement payload bundled into each item, and a credit cost of 1 per call, which is useful for budgeting. It stops short of stating page size or how pagination terminates.

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?

A single front-loaded sentence plus a parenthetical cost note; nothing is padded or redundant. It is arguably over-compressed, since a few more words on pagination would have earned their place, but no sentence is wasted.

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 three-parameter read-only list tool with full schema coverage and no output schema, the description covers what the results contain and their order. It omits how many posts a page returns and any rate-limit or auth context, which leaves an agent guessing about call volume and credit burn across paginated calls.

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% and the schema already explains that user_id is a DID and that you should send either it or handle, plus how cursor is sourced from data.cursor. The description adds nothing about parameters, so the baseline of 3 applies — the schema carries the full burden here.

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 names a specific resource and scope: a single profile's posts, returned newest first, with engagement fields (likes, replies, reposts). An agent can distinguish it from bluesky_post (single post) and bluesky_profile (profile metadata), though the phrase is nominal with no explicit verb like 'list' or 'fetch'.

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 when-to-use statement, no prerequisites, and no mention of alternatives such as bluesky_post or twitter_user_tweets for equivalent tasks. The agent must infer from the tool name alone that this is the timeline-listing call for a Bluesky account.

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