list_saved_sites

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

Description discloses the tool is read-only (FREE with a key) and returns an array of saved sites with specific fields, complementing the readOnlyHint annotation. It adds context about the persistent shortlist built by save_site, but could further clarify if the list is sorted or if there are 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?

The description is concise yet comprehensive: one paragraph front-loading the purpose, providing examples, listing return fields, and clearly excluding sibling tools. 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?

Given no output schema and parameter count of 0, the description fully explains the return value and its structure. It mentions the tool is free with a key and clarifies usage boundaries. Complete for its simplicity.

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?

No parameters exist; schema coverage is 100%. The description adds value by explaining what the tool returns (array of saved sites with name, market, etc.), compensating for the lack of an output schema. Baseline 4 for zero params.

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?

Description clearly states the tool's purpose: 'Use when a user asks to see or review their saved DC Hub shortlist in-chat' and provides specific examples. It specifies the return value (array of saved sites with fields) and distinguishes from sibling tools like save_site and export_dataset.

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?

Explicitly states when to use (user asks to see/review shortlist) and when not to use (to add a site use save_site, to download as file use export_dataset). Provides clear guidance with examples.

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