list_saved_searches

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

No annotations provided, so description carries full burden. Mentions results are limited to accessible searches, which is important. However, does not disclose pagination, sorting, or response fields like ids/names. For a read-only list tool, this is adequate but could be richer.

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?

Three sentences with no redundancy. First sentence states purpose and metadata, second gives usage context, third clarifies access limitation. Front-loaded and 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?

Covers purpose, filtering options, and scope (accessible searches). For a list tool without output schema, it provides sufficient context. Lacks details on return format but is acceptable given parameter descriptions and no output schema.

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 baseline is 3. The description reinforces filtering by owner/app/sharing but adds no new semantics beyond the schema. Parameters are well-documented in the schema itself.

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 'List saved searches' with specific metadata details (ownership, schedule, visibility, permission). Distinguishes from sibling tools like get_saved_search_details and execute_saved_search by focusing on discovery and filtering, not execution or detail retrieval.

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 says 'Use this to discover available reports/automations and to filter by owner/app/sharing.' Provides clear context for when to use, but does not explicitly exclude alternatives like get_saved_search_details for detailed views.

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