Workbooks Delete Workbook Embed

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuine context beyond annotations: the mandatory confirm=True gate and the specific consequence that embeds using the embed URL stop working.

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 short sentences with no waste, each contributing a distinct fact: the operation, the confirmation requirement, the source of IDs, and the side effect. The core action 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?

With an output schema present, return values need no explanation, and the description covers prerequisites and consequences of a destructive mutation. It is nearly complete, lacking only a note on workbook_id semantics or error behavior.

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 0%, so the description must compensate, and it explains the confirm parameter's required value plus how to obtain embed_id. The workbook_id parameter is left implicit, which is a minor gap for a three-parameter tool.

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 ('Delete an embed from a workbook') and implicitly distinguishes itself from the listing sibling by telling the agent where embed IDs come from. An agent can identify the operation and its target without opening the schema.

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?

Names the sibling tool to use for obtaining embed IDs and states the required confirm=True precondition, which is concrete routing guidance. It does not describe when deletion should be avoided or what alternatives exist beyond listing, but 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.