list_saved_searches

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

No annotations are provided, so the description carries the full disclosure burden. It hints that each entry carries a new-items counter, but says nothing about whether this is a read-only operation (implied only by 'list'), whether authentication is required, how results are ordered, or how 'recent' is defined.

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?

One compact phrase, front-loaded with the resource and the key distinguishing output detail. It is a sentence fragment and leaves 'recent' undefined, but no words are wasted.

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 zero-parameter list tool with no output schema, the description covers what is enumerated and one notable return field. It stops short of clarifying what separates 'recent' from 'saved' entries or what the calling context (signed-in user?) is, leaving a small but real gap.

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 takes zero parameters, so the empty schema is self-explanatory; the baseline for a no-argument tool applies. The description adds no parameter meaning because there is none to add.

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?

Names the resource precisely ('Recent and saved (alert) searches') and adds the distinguishing detail of 'new-items counters', which separates it from generic search siblings like search or suggest. The listing verb is only implied by the tool name rather than stated, keeping it short of a 5.

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?

No indication of when to call this versus search, search_filters, or unread_counts, and no stated prerequisites or exclusions. The agent must infer the use case purely from the phrase 'saved (alert) searches'.

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