list_saved_sites

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds valuable behavioral detail: the 'since' parameter controls delta window, output includes deltas like verdict changes and portfolio summary. No contradiction with annotations.

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?

Well-structured: front-loaded with use case and example, then parameter details, then return value breakdown. Every sentence adds value, though could be slightly more concise without losing information.

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?

Without an output schema, the description thoroughly lists return fields (name, market, lat/lon, DCPI, target MW, notes, plus live deltas). It covers verdict changes, power move, DCPI comparison, alerts, new facilities, portfolio summary. Sufficient for understanding tool behavior.

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?

Single parameter 'since' is fully described in the schema (100% coverage). Description adds context: default value '7d', format options ('24h', ISO timestamp), and hint to pass cached generated_at. This goes beyond the basic schema description.

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 explicitly states 'Use when a user asks to see or review their saved DC Hub shortlist in-chat' and provides concrete examples. It also distinguishes from siblings by specifying not to use for adding (save_site) or exporting (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?

Clear when-to-use (reviewing saved sites, checking movement) and when-not-to-use (adding or downloading). Includes example queries and explicit references to alternative tools.

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