archive_toggle

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

No annotations are provided, so the description fully carries the burden of behavioral disclosure. It details recursive search, case-insensitive trimming, archiving the container block without individually deleting children, and the dry_run option. It does not contradict any annotations.

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?

Three sentences effectively convey purpose, search details, and missing title behavior. Front-loaded and no unnecessary words, but could be slightly more compact.

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?

Given the tool's simplicity (3 params, no output schema), the description covers main behaviors and the dry_run option. However, it does not detail the return format on success/failure, which would enhance completeness. Comparisons or integrations with sibling tools like restore_toggle are missing.

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%, providing parameter descriptions. The description adds significant meaning beyond the schema for the 'title' parameter by describing the search behavior and block types matched. For 'dry_run', it restates the schema's description, adding no new value.

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 clearly states the tool archives a toggle by title from a page, specifying the action, object, and source. It distinguishes from siblings like archive_page by focusing on a single toggle and explains what constitutes a toggle (plain toggle blocks and toggleable headings).

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 description mentions that missing titles return available toggle titles, providing some guidance, but lacks explicit when-to-use vs alternatives like restore_toggle or update_toggle. No direct comparisons or exclusions.

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