create_saved_search

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

Mentions outputs (creation status, applied configuration) and security constraints, but lacks details on failure behavior, idempotency, potential overwrites, or side effects. With no annotations, the description should be more thorough.

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 front-loaded purpose, then outputs and security. No fluff, every sentence adds value.

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?

With 10 parameters, no output schema, and no annotations, the description covers only a fraction of the tool's complexity. Missing explanation of time range, app, visibility, and search string format.

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 coverage is 0%, so description must explain parameters. Only hints at scheduling and sharing, leaving most parameters (name, search, time range, app, visibility) unexplained.

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?

Clearly states the tool creates a saved search (report/automation) with optional scheduling and sharing, using the verb 'create' and specifying the resource. Distinguishes from sibling tools like update_saved_search and delete_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?

Implies usage for persisting SPL queries and scheduling, but does not provide explicit when-to-use vs. alternatives, nor prerequisites or permissions. No guidance on when not to use this tool.

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