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

No annotations are provided, so the description carries the burden of conveying behavior. The verb 'List' implies a read-only operation, and the phrase 'inspect before publishing' adds context that contents are drafts. However, it does not disclose other behavioral details like side effects or return format, which is acceptable for a simple list tool but not richly detailed.

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 sentence with a parenthetical clarification, front-loading the primary action 'List what is currently in your basket'. Every word serves a purpose, with no redundancy or filler.

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?

Given the tool has no parameters, no output schema, and no annotations, the description adequately covers its purpose and usage. It is a simple read operation, and the description provides enough information for an agent to select and invoke it correctly, including the timing (before publishing).

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 input schema has zero parameters, so there is nothing to document. The baseline for a zero-parameter tool is 4, and the description adds no parameter information because none exists; this is appropriate.

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 lists the current basket contents, using the specific verb 'List' and resource 'basket'. It also clarifies the items are drafted articles/placements for inspection before publishing, which distinguishes it from the sibling publish_basket tool.

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 provides the context 'before publishing', implying the tool is used for inspection prior to a publish action, and thus differentiates it from publish_basket. However, it does not explicitly name alternatives or exclusions, though the use case is clear.

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