set_min_score

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

With no annotations, the description carries the full burden. It states the mutation (set) and the setting's range/default, but does not disclose side effects, persistence, scope (global vs per-user), or whether it affects existing searches. It is not misleading, but lacks behavioral detail beyond the immediate action.

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?

A single sentence conveys the operation, range, and default with zero excess. The action verb is front-loaded, making it immediately scannable.

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 simple one-parameter setter with no output schema, the description is largely complete. It covers the key semantics (range, default). It could mention persistence or effect on subsequent searches, but that is a minor omission given the tool's simplicity.

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 the description must compensate. It explains the meaning ('vacancy-to-resume match score') and the range (0-100), which goes beyond the schema's simple number with min/max. It does not name the parameter 'minScore' explicitly, but with a single parameter, that is implied.

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 verb 'Set', a specific resource 'minimum vacancy-to-resume match score', and the value range (0-100). It clearly distinguishes from siblings like get_settings (retrieval) and set_browser/set_resume (other settings).

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 usage is implied: this tool sets a threshold before searching for vacancies. It does not explicitly state when to use it vs alternatives, nor does it mention exclusions or prerequisites. The default of 70 gives a hint but no direct guidance.

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