Create or update tax

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the description is not responsible for those. It adds the create-vs-update behavior based on id, which is useful. However, it does not disclose what happens on update (full replace vs merge) or how missing IDs are handled, leaving some behavioral ambiguity.

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?

A single sentence that is front-loaded with the action and resource, with no filler. Every word earns its place.

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 tool with 5 parameters, 3 required, no output schema, and low schema coverage, the description is thin. It does not address how to obtain existing tax IDs (e.g., via list_taxes), what happens when an ID is invalid, or constraints on rate/type beyond the schema enum. An agent may be uncertain about edge cases.

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 only 40% (id and rate have descriptions). The description clarifies the id parameter's role (omit to create, pass to update) but does not add meaning for name, type, or stores. It partially compensates for low coverage but leaves the other parameters dependent on the schema's limited info.

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 the verb (create/update) and resource (tax rate) explicitly, and distinguishes the two modes via the id parameter. It clearly separates this tool from the read-only list_taxes and other upsert 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 purpose implies when to use it (creating or updating a tax), but it does not explicitly state when not to use it, mention alternatives like list_taxes for finding existing IDs, or note any prerequisites. Usage guidance is implied rather than explicit.

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