update_tax_rate

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

The annotation idempotentHint=true already covers idempotency. The description adds key behavioral context by specifying that only included fields are changed, meaning unspecified fields remain untouched. This goes beyond the annotation and is valuable for safe invocation.

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 two short sentences: 'Update a tax rate. Only include fields you want to change.' It is concise, front-loaded, and contains no unnecessary information.

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 the 12-parameter schema and lack of output schema, the description provides the essential purpose and update behavior. It could mention return values or error conditions, but the available context (annotations, full schema) makes it adequate for correct invocation.

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 all 12 parameters have descriptions. The description adds meaning by clarifying that only fields to change should be included, reinforcing that id is the only required parameter and others are optional.

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 updates a tax rate, using a specific verb and resource. The added note 'Only include fields you want to change' indicates partial update semantics, distinguishing it from create/delete/get/list siblings.

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 implies usage for modifying existing tax rates identified by id. It provides guidance on partial updates but does not explicitly exclude other tools or state when not to use it. However, sibling tool names make the comparison obvious.

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