Create Saved Search

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

With no annotations, the description carries the burden of behavioral transparency. It discloses the output ('creation status and the applied configuration') and security constraints ('visibility and execution are constrained by permissions and chosen sharing level'). These add value beyond the schema and cover the key behavioral aspects, though it does not detail side effects such as overwriting existing searches.

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 compact, consisting of two sentences that immediately state the purpose and then provide output and security notes. It is well-structured, front-loaded, and free of unnecessary detail.

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 tool with 10 parameters and no output schema, the description is under-specified. It gives the purpose and some security context but does not explain scheduling syntax (cron), sharing level meanings, app assignment, or the role of time parameters. This leaves significant gaps for an agent invoking the tool correctly.

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 schema description coverage is 0% for 10 parameters, so the description must compensate. However, it only vaguely mentions 'optional scheduling and sharing' without explaining the meaning of parameters like earliest_time, latest_time, app, description, or is_visible. It fails to provide sufficient meaning for most parameters, requiring the agent to infer or inspect the schema.

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 tool creates a saved search with optional scheduling and sharing, using the verb 'create' and resource 'saved search'. It distinguishes from siblings like delete_saved_search, update_saved_search, execute_saved_search, and list_saved_searches by focusing on creation.

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 explicitly says 'Use this to persist useful SPL queries and optionally schedule them via cron,' providing clear context for when to use it. It does not explicitly mention alternatives or state when not to use it, but the create verb makes the usage scenario unambiguous.

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