list_taxes

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered by structured data. The description adds only 'with rates', which is a return-content hint largely duplicated by the output schema, and discloses nothing about scoping or completeness.

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?

It is only six words, so it cannot be accused of padding, but it is a sentence fragment rather than a front-loaded statement of action. Brevity here reflects under-specification more than efficiency.

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 trivial, zero-parameter list tool with full annotations and an output schema, very little prose is required, and the description's silence on return shape is acceptable. Still, it never states that all configured taxes are returned unfiltered, which is the one fact an agent would want.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The phrase 'with rates' adds a small amount of meaning about what each returned tax object includes.

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 fragment 'Sales taxes configured, with rates' identifies the resource (sales tax configurations) and hints at returned rates, so an agent can infer it's a list operation. However, there is no verb and no explicit statement that it enumerates all records, leaving the purpose implied rather than stated.

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?

No guidance is given about when to call this versus siblings such as list_reference or api_get, nor any prerequisites or exclusion conditions. The description offers no routing information at all.

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