shared_budget_delete_preview

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

The annotations already declare readOnlyHint=true, destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds useful context by calling the deletion 'irreversible' and noting the budget must be 'unassigned,' but it does not resolve the internal tension between readOnly and destructive or explain that the preview itself is non-mutating.

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 a single front-loaded sentence with no wasted words. It immediately communicates the action, the resource, and the irreversibility constraint.

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?

An output schema and rich annotations reduce what the description must carry, and the description supplies the irreversible/deletion context and the unassigned precondition. However, for a destructive preview tool, it is still thin on how the preview relates to the eventual deletion, what expectedText is for, and what the id identifies.

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 75%, with profile, adAccountId, and expectedText described in the schema, while id is undocumented in both places. The description contributes no additional parameter meaning, and it does not explain that expectedText appears to act as a safety confirmation against the current resource name.

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 a specific verb and resource: 'Preview irreversible deletion' of a 'shared budget,' with the scope narrowed to 'one unassigned LOC shared budget.' It is clear what action is being previewed, but it does not distinguish this tool from siblings such as shared_budget_get or shared_budgets_query.

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?

There is no explicit guidance on when to choose this preview versus shared_budget_get, shared_budgets_query, or how to proceed to an actual deletion. The word 'unassigned' implies a precondition, but no alternatives, exclusions, or next-step workflow are provided.

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