Create Budget Modification

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

Annotations provide readOnlyHint: false, destructiveHint: false. The description adds the precondition (only if Budget Changes not enabled), deprecation date, and that it returns HTTP 201 with the created object. It also mentions the endpoint and API category, which is useful context beyond 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?

The description is a single paragraph with multiple sentences, but contains redundancy (e.g., 'Creates a Budget Modification...' and then 'Use this to create a new Budget records...' and again 'Creates a new Budget records...'). While each sentence adds some value, the repetition could be streamlined.

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 7 parameters and no output schema, the description explains the condition and deprecation but does not cover optional parameters, default values, error scenarios, or the response structure beyond 'returns the created object'. This leaves gaps for a creation tool.

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%, so baseline is 3. The description lists the three required parameters (project_id, to_budget_line_item_id, transfer_amount) but adds no additional meaning beyond what the schema already provides. The schema descriptions are detailed, so the description does not enhance understanding.

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 creates a Budget Modification, with a specific condition (only if Budget Changes are not enabled) and deprecation notice, distinguishing it from the Budget Changes API. The verb 'creates' and resource are explicit, and the condition differentiates it from sibling tools.

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 explicitly states when to use (only if Budget Changes not enabled) and implicitly when not (use Budget Changes API instead). It provides a direct link to documentation for upgrading, offering clear guidance on alternatives.

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