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

Annotations declare idempotentHint=false and destructiveHint=false, which the description confirms by stating 'Add' (create operation). The description does not disclose additional behavioral traits such as error handling on duplicate titles or return value details.

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?

The description is concise (three sentences) with no extraneous information. It is front-loaded with the purpose and efficiently covers the required and optional fields.

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?

The description covers the creation action and lists parameters, but since there is no output schema, it lacks information about what the tool returns (e.g., success indicator, created method ID). Given the tool's simplicity, it is adequate but not comprehensive.

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 descriptions exist for all parameters in the schema. The tool description lists parameters but adds only minimal extra context (e.g., 'cashboxLock (0 = all cashboxes)') beyond what the schema provides.

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 'Add a new payment method to the shop' with a specific verb and resource. It distinguishes itself from sibling tools like payment_mode_delete (deletion) and data_list_payments_modes (listing), enabling correct selection.

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 indicates that a title is required and lists optional fields. It suggests using data_list_payments_modes to list existing methods, providing context. However, it does not explicitly exclude scenarios or mention prerequisites like permissions.

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