shared_budget_create_preview

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds useful context that the preview uses a private local billing profile, but it does not further explain what is persisted, what permissions are required, or what the preview evaluates.

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 definition is a single front-loaded sentence with no filler, and it leads with the core action: previewing shared-budget creation. It is appropriately concise, though the terseness leaves important required-parameter context unstated.

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?

This is a complex preview tool with six required parameters, a nested value object, low schema description coverage, and an output schema. The description does not provide enough input context for an agent to populate the required fields correctly, even though annotations and the output schema reduce the need to explain safety and return values.

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 only 29%, with seven parameters and six required, so the description needs to carry more meaning than it does. It only vaguely gestures at the billing profile concept and does not explain the required name, value amount/currency, startTime/endTime, profile, or adAccountId semantics.

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 names a specific operation, previewing shared-budget creation, and identifies the mechanism as a private local billing profile. It is not a tautology and separates the tool from query/get/update/delete siblings. However, 'LOC' is unexplained and the description does not explicitly differentiate this preview from the broader shared-budget workflow.

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 word 'Preview' implies this is a dry-run-style tool to use before actual shared-budget creation, which gives an implied usage context. But the description does not state explicit when-to-use conditions, prerequisites, or alternatives such as shared_budgets_query or the update/delete preview siblings.

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