Display List

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

With no annotations, the description carries full burden. It discloses features like interactivity and customization but doesn't explicitly state read-only behavior or absence of side effects. While likely non-destructive, more explicit transparency would help.

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 relatively concise with two sentences. It front-loads key features and purpose. Minor redundancy (e.g., 'any type of list' could be implied) but overall efficient.

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 6 parameters, no output schema, and a display tool, the description provides a solid overview of features and use cases. It covers core capabilities, though lacks explicit mention of return value (likely void). Still adequately complete.

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%, so schema already describes each parameter. The description adds general feature context but doesn't enhance parameter meaning. Baseline 3 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 it displays an interactive, customizable list with specific features like checkboxes, drag-and-drop, images, and export. It distinguishes from sibling tools by listing unique capabilities not present in display_chart or display_table.

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 says 'Perfect for displaying any type of list' and lists features, implicitly differentiating from siblings. However, it lacks explicit when-not or alternative tool guidance, though the context is clear.

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