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

No annotations are provided, so the description carries the full burden. The verb 'List' clearly indicates a read-only operation, and the parenthetical adds context about inspecting drafted content. It doesn't disclose return format or pagination, but for a simple list operation, the description sufficiently conveys non-mutating behavior.

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. The main action ('List what is currently in your basket') is stated first, followed by a parenthetical clarification. No wasted 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 simple tool with no parameters and no output schema, the description covers the main aspects: what it does and when to use it. It doesn't specify return values, but the verb 'List' implies the output is the basket contents, which is sufficient for this simple 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 has zero parameters, so the schema provides all needed info. The description adds meaning by explaining the purpose (basket inspection), which complements the empty parameter schema. Baseline for 0 params is 4.

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 uses a specific verb ('List') and resource ('your basket'), and clarifies the scope as 'drafted articles/placements before publishing.' This clearly distinguishes it from sibling tools like publish_basket or order_backlink.

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 'before publishing' gives clear usage context: use this to inspect the basket prior to publishing. It implicitly differentiates from publish_basket, though it doesn't explicitly name alternative tools or say when not to use it.

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