release_search_scroll

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

Annotations declare readOnlyHint=false and destructiveHint=false, consistent with a non-destructive resource cleanup, and the description adds the useful behavioral fact that freeing must cover every page opened. It does not disclose idempotency, error behavior on stale tokens, or the cost of leaking a session, so it is not fully transparent.

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 tightly written sentences: the purpose/trigger first, then the payload shape. No filler, and the most decision-relevant information is front-loaded.

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 single-parameter cleanup tool with no output schema, the description covers purpose, trigger, and payload shape adequately. A note on what happens to un-released tokens or error handling would make it fully complete.

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% – the schema already documents the scrollId → scrollToken map. The description's embedded format example and 'for every page you opened' marginally reinforce it but add little beyond the structured field, so the baseline 3 is appropriate.

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 gives a specific verb ('Free') and resource ('scroll-search resources') and ties it to a concrete trigger ('when you stopped paging through a scrolled find_issues result'). It is clearly distinguishable from siblings, none of which release scroll sessions. It stops short of 5 only because there is no explicit sibling contrast to anchor it further.

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?

It states a clear when-to-use condition: after you have stopped paging through a scrolled find_issues result. The instruction 'for every page you opened' further tells the caller the required scope of the call. No when-not-to-use guidance or mention of consequences for skipping the call, which keeps it below 5.

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