Create modifier

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

With no annotations provided, the description carries full burden. It reveals it is a POST request (mutating) and how 400 errors are handled, but does not disclose authentication needs, rate limits, or side effects beyond creation.

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: first states purpose and endpoint, second provides error handling. No excess verbiage; front-loaded with core 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?

For a creation tool with a nested body parameter, the description points to external docs and error handling. However, it does not describe the return value, idempotency, or required fields within the body, leaving gaps.

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 schema has one object parameter with no enumerated properties; the description adds that field names follow the Loyverse API docs and explains error handling. This adds meaning beyond the schema, though it relies on external documentation for specifics.

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 'Create a new modifier in Loyverse (POST /modifiers)'. This specifies the verb and resource, and the sibling tools include other 'create' tools, so it distinguishes itself by being for modifiers specifically.

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 provides error handling guidance for 400 responses but does not indicate when to use this tool versus alternative create tools (e.g., loyverse_create_item). No prerequisites or context are given.

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