delete_library_sections_all_refresh

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

The annotations already indicate destructive, idempotent, and not read-only. The description adds no extra behavioral context about what stopping the refresh involves, such as whether it cancels already-running refreshes, the scope of 'all', or potential side effects. It merely repeats the core 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?

The description is extremely concise: a two-line snippet with the action followed by the endpoint. No filler or irrelevant text. It is appropriately minimal for a no-parameter, single-purpose tool.

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?

The tool is simple, but the description does not state that the refresh applies to all library sections, which is a meaningful distinction from the sibling delete_library_sections_by_section_id_refresh. While the URL contains 'all', the natural-language description omits this scope. Output schema exists, so no need to explain return values, but the missing scope detail leaves an agent less informed.

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?

Since there are zero parameters and schema coverage is 100%, the baseline of 4 is appropriate. The description has nothing to add about parameter meaning; the tool takes no arguments.

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 'Stop refresh' as the verb-action, and the accompanying endpoint clarifies the resource as the refresh endpoint for all library sections. However, it does not explicitly name or distinguish from the similar sibling delete_library_sections_by_section_id_refresh, and the phrase 'all' only appears in the URL, not in the natural-language description.

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?

No guidance is provided on when to use this tool versus alternatives like the section-specific deletion or the create/refresh triggers. The description is a bare command with no discussion of use cases or exclusions.

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