careers_save_search

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

The description goes well beyond the annotations by explaining the validate-then-save flow, local-only scope, absence of portal alerts or scheduled actions, and the precise semantics of replace=true overwriting only the named local definition. This gives the agent a clear side-effect model.

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 short sentences, front-loaded with the core action, followed by exclusions and replace behavior. Every sentence adds distinct value and there is no filler.

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 mutating tool with an output schema, the description covers validation, local-only persistence, side-effect exclusions, and replace semantics well. It is slightly incomplete on parameter meanings and on when to choose this over sibling search-related tools, but the output schema and parameter names fill some gaps.

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%, so the description needed to compensate, but it only explains replace=true. The other seven parameters, including query, filters, sort, source, ascending, and all_statuses, are left to inference from their names and enum values.

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 states a specific action ('save') and a specific resource ('credential-free LOCAL search preset'), and distinguishes it from portal alerts and scheduled sends. It also clarifies the CLI sharing, making the tool's role unmistakable even among many sibling 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?

The description clearly says this should run 'only when requested,' which gives an explicit usage boundary. It also states what the tool does NOT do, but it does not name an alternative tool or describe when to prefer a sibling like careers_searches or careers_check_search.

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