Update Saved Search

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

Annotations already provide destructiveHint and idempotentHint. The description adds that it is a 'partial update' and references the query syntax from another tool, which are useful but not extensive. It doesn't disclose side effects, permission requirements, or error conditions.

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 two sentences long, front-loaded with the core purpose, and each sentence provides value without redundancy. It efficiently communicates the partial update requirement and query syntax reference.

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?

The description lacks details about the request_id parameter, return behavior (though output schema exists), and error handling. For a tool with 5 parameters and 0% schema coverage, more context would help, but the output schema partially compensates.

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?

With 0% schema description coverage, the description covers 3 of 5 parameters (name, query, description) by stating they are optional and that at least one is required. The query parameter's format is linked to another tool. The request_id parameter is not mentioned, leaving a gap.

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 updates an existing saved device search and specifies it is a partial update. The verb 'Update' and resource 'saved device search' are specific, but it does not explicitly differentiate from other sibling tools like create_saved_search or delete_saved_search, though the name and context make it clear.

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 advises to provide at least one of name, query, or description, which guides usage. However, it does not specify when not to use this tool (e.g., when to use create_saved_search instead) or mention any prerequisites like the saved search must exist.

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