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

Annotations already declare this a safe, non-destructive, non-open-world read. The description adds genuinely new behavioral context: authentication is required, results are ordered newest first, entries carry editor links, and the currently open design is surfaced first and flagged open_now. It omits pagination or result-size limits.

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?

Three short sentences, front-loaded with what is returned before the auth and ordering details, with no padding. The final clause about the editor's open design is slightly convoluted but earns its place by naming the open_now marker.

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?

With no output schema, the description must carry the return-value burden, and it does: ordering, editor links, and the open_now field are all disclosed. Only pagination/limits and sibling differentiation are missing, which are minor for a zero-parameter list 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?

The tool takes zero parameters, so the baseline is 4 per the rubric. There is nothing further for the description to clarify about inputs.

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 states a specific resource (the user's Renderball documents) and its key attributes: newest-first ordering, editor links, and an open_now marker. It never names a sibling like see_deck or deck_status, so the agent must infer the distinction from the name alone, but the returned resource is unambiguous.

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?

It states a prerequisite ('Needs an account (a key)') and implicitly scopes results to the authenticated user, which is useful. However, it gives no guidance on when to prefer this over see_deck or deck_status, so usage is only implied.

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