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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is largely covered. The description contributes real context by clarifying the search itself is untouched ('The search keeps running') and by stating the 200-record ceiling. It omits what an agent most needs for a non-idempotent copy: whether repeat calls duplicate records or skip already-kept ones.

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 sentences, front-loaded with the action and closed with the non-obvious side effect (the search keeps running). No filler, no restatement of the title, and the 200/limit clause is compactly parenthesized.

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?

With no output schema, the description should say what comes back — created record ids, a count, or nothing — and whether partial results occur near the 200 cap. Combined with the silent duplicate-handling question for a non-idempotent write, a meaningful gap remains for a mutation tool.

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 100%, so the schema already defines all three parameters. The description nevertheless reinforces the important semantic — 'limit' selects the newest N rather than an arbitrary N — which aligns with the schema's parenthetical and reduces the chance of a mis-set limit. Slight overlap keeps it just below the top score.

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 and resource ('copies a saved search's newest matches into its folder as records') and adds the scope cap. The action is distinguishable from the read-oriented siblings (get_search_matches, list_folders) by the word 'copies...as records', though it never names those siblings explicitly.

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?

Usage is implied rather than stated — an agent can infer this is the persist-the-results action while get_search_matches merely reads them. There is no explicit when-not guidance, no mention of how it relates to save_search_to_folder or add_to_folder, and no prerequisites described.

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