Update modifier

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

Discloses key behavioral traits: not a partial patch, error handling returns Loyverse's error message verbatim. Since no annotations exist, the description adequately covers mutation behavior, though it could mention idempotency or side effects.

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 that are succinct and front-loaded with the action. Every sentence provides essential information without redundancy.

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 no annotations, the description covers the key behavioral aspects and parameter constraints. It could mention the response format (e.g., returns updated modifier) and prerequisites (having an existing id), but overall it's fairly complete.

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 baseline is 3. The description adds meaning by clarifying that body must contain all required fields, not just changes, and refers to API docs for field names, compensating for the generic object schema.

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 explicitly states 'Update an existing modifier' and explains the HTTP method and endpoint, clearly distinguishing it from create_modifier and other update tools for different resources.

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?

Provides important guidance on not using partial patches and including all required fields, as well as handling 400 errors by adjusting and retrying. However, it could be improved by explicitly contrasting with create_modifier.

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