create_saved_search

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

With no annotations provided, the description discloses outputs ('creation status and applied configuration') and security constraints ('visibility and execution constrained by permissions and sharing level'). It does not detail potential side effects like overwriting or trigger conditions, but covers key behavioral traits.

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 three focused sentences: purpose, usage, and then bullet-like outputs and security. No extraneous information, and front-loaded with key action and resource.

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 the complexity (10 parameters, no output schema, no annotations), the description lacks detail on parameter meanings, error conditions, and success/failure behavior, making it insufficient for an AI agent to use correctly without additional context.

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 0% with 10 parameters. The description only broadly references scheduling and sharing, failing to explain semantics for parameters like earliest_time, latest_time, cron_schedule, is_visible, and app.

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 the verb 'create', the resource 'saved search (report/automation)', and optional features like scheduling and sharing, distinguishing it from siblings like update_saved_search and execute_saved_search.

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 tells when to use ('persist useful SPL queries and optionally schedule them via cron') but does not explicitly state when not to use or mention alternatives such as update_saved_search for modifications.

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