payments_create_prescription

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a create operation but does not explain side effects, required amount/currency relationships, default values like state=1 or direction=1, or what happens if per-person amounts partially cover the required fields.

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 a single sentence with no waste. It states the core action and the key optional capability compactly.

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 tool with 12 parameters, no annotations, and no output schema, a one-sentence description is insufficient. It omits important context such as required amount unless per-person amounts are set, default states and directions, and expected behavior or return value.

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 description coverage is 58%, so the schema handles most parameter meanings. The description adds value by explaining that per-person amount overrides are supported, which clarifies the optional amount field. However, it does not help with undocumented parameters like is_credit, category_id, specific_symbol, or previous_prescription_id.

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 states a specific verb and resource: 'Create a new payment prescription', which clearly distinguishes it from sibling tools like payments_create_payment, payments_update_prescription, and payments_delete_prescription. The per-person amount override detail adds useful scoping beyond the tool name.

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 gives no guidance on when to choose this tool over alternatives such as payments_create_payment or payments_update_prescription. It does not mention prerequisites, conditions for creation, or when per-person overrides are appropriate.

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