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

The description reveals a non-obvious behavior: "Scripts are injected when the page is next saved in the editor or published; the change is not live on an already-published page until then." This deferred effect is critical for the agent to know, and since annotations only provide readOnlyHint: false, this addition is valuable and non-redundant.

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, all essential, with the core action up front and zero fluff. The information about list_scripts and the injection timing are both high-value additions.

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 2-parameter tool with a clear output schema, the description covers the key context: how to get the ID, and the behavioral timing. No critical gaps.

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 the baseline is 3. The description reinforces that scriptId should come from list_scripts, which aligns with the schema information but adds no substantial new semantics beyond what's already in the schema.

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 starts with a specific verb+resource: "Detach a third-party script from a page." This action is distinct from sibling tools like remove_webhook, and the title reinforces the operation clearly.

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 provides a clear usage hint by directing the user to obtain scriptId from list_scripts. However, it does not explicitly state when to use this tool versus alternatives (e.g., when to remove a webhook instead), though the context is clear.

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