load_search_filter

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

With no annotations, the description must disclose behavioral traits. It only states 'Load saved search filters', implying retrieval but not specifying whether it is read-only, how it handles multiple parameters, error states, or return format. Critical behavioral context is missing.

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 only four words, which is too terse. It lacks structure or front-loading of key information. While brevity is valued, it sacrifices clarity and fails to provide necessary details.

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 tool has two optional parameters and no output schema, the description is severely incomplete. It does not explain return values, behavior when both parameters are given, or any constraints. The agent cannot infer correct usage from this alone.

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%, and the description provides no explanation of the two optional parameters (filter_id and filter_name). The agent has no guidance on what these parameters represent, their relationship, or typical usage. This is a complete lack of semantic information.

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 'Load saved search filters' uses a clear verb 'Load' and specifies the resource as 'saved search filters', which differentiates it from sibling tools like 'save_search_filter'. However, it could be more precise about what 'load' entails (e.g., retrieve, display, apply) and lacks detail to fully distinguish from similar retrieval tools.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like 'search_insights_by_scope', nor does it explain conditions for using filter_id vs filter_name. This leaves the agent without context for proper selection.

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