Create tax

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

No annotations provided, so description carries full burden. It discloses that 400 errors return verbatim messages and suggests retrying with adjustments. However, it omits idempotency, duplicate handling, authorization needs, and return value behavior.

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?

Two sentences, front-loaded with purpose, then error guidance. No unnecessary words. Could be slightly more structured, but very efficient.

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 no output schema and 1 nested parameter, the description lacks explanation of the return value or expected fields beyond a link to docs. With many sibling tools, no comparative context is provided. Missing critical details for effective use.

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?

Input schema has one parameter 'body' with description referencing the API schema. The description adds a link to API docs and error handling hint, but does not specify required fields or valid values. Schema coverage is 100%, baseline is 3; description provides marginal added value.

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 action ('Create a new tax') and the resource ('in Loyverse') with the HTTP method (POST /taxes). It effectively distinguishes from sibling update and delete 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?

No explicit guidance on when to use this tool versus alternatives (e.g., update_tax). The description only mentions error handling, but does not explain prerequisites or context for creation.

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