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

Annotations already mark the operation as destructive, but the description adds the important nuance of a 'soft delete,' which is genuinely informative beyond the annotation. It also states that a confirmation of deletion is returned, giving a bit of behavioral context.

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 main purpose is front-loaded in the first sentence, and the rest is a compact Args/Returns structure. It is slightly redundant because the Args section repeats the schema, but it remains short and readable.

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 one-parameter soft-delete operation with a destructive annotation, the description is minimally adequate: it names the resource, the parameter, and the return type. However, it leaves the meaning of 'soft delete' vague and gives only a generic confirmation as the return value, with no output schema to fill that gap.

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?

The only parameter description, 'budget_id: The ID of the budget to delete,' essentially restates the schema property title 'Budget Id.' It adds no guidance on how to obtain the ID, its format, or any validation rules, so it does little to compensate for the schema description coverage of 0%.

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 action and resource: 'Delete a budget (soft delete).' This is clear and distinct from nearby siblings like update_budget or list_budgets, though it does not explicitly name or contrast any sibling.

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 guidance about when to use this tool versus alternatives such as update_budget, deactivating a budget, or other delete operations. No context, prerequisites, or exclusions are provided.

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