search_presets

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds the auth requirement, which is useful. However, it says 'free servers' while the scope parameter permits 'all', an unresolved inconsistency, and it says nothing about result volume or pagination for an open-world search.

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?

Two short sentences, front-loaded with the core action and ending with the prerequisite. No filler, though the phrasing is terse enough to leave the free/all scope question unaddressed.

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 read-only search with a fully documented schema and no output schema, the description covers the essentials plus the auth requirement. It falls short on clarifying the free-vs-all scope distinction and how the results relate to the preset listing tools.

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 100%, so name, scope, and location are all documented in the schema, including the enum and the free/all distinction. The description only repeats the vm.pico example already present in the schema and adds no new syntax or format meaning. Baseline 3 applies.

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?

States a specific verb (Search) and resource (free servers matched by preset name) with a concrete example (vm.pico). It is distinguishable from list_presets/get_preset in spirit, but it never names those siblings, so the differentiation must be inferred.

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?

Only prerequisite given is 'Requires auth.' There is no statement of when to use this over list_presets, get_preset, or list_stock_servers, nor any exclusion guidance. Usage is implied by the phrase 'matching a preset name' but not articulated.

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