payments_list_prescriptions

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only states 'List payment prescriptions with optional filters' and does not describe what the response contains, whether results are paginated or ordered, how filters interact, or any read-only guarantees. 'List' implies read-only behavior, but the effect is not truly disclosed.

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, direct sentence with the operation front-loaded and no filler. It is appropriately sized given that the schema handles the parameter details.

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 read-only list tool with complete parameter descriptions, this is minimally viable. However, with no output schema and no annotations, it leaves the agent to infer the response shape and possible pagination or scoping behavior, which is a clear gap for a tool that presumably returns a collection.

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 input schema already documents all 8 parameters with 100% coverage, so the description does not need to add much. The phrase 'optional filters' adds no semantic detail beyond what the schema already provides, so the baseline of 3 is appropriate.

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 uses a specific verb ('List') and a clear resource ('payment prescriptions'), making the operation unambiguous. It is naturally distinguished from the sibling tools payments_create_prescription, payments_update_prescription, and payments_delete_prescription, which represent different actions on the same resource.

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 implicitly communicates when to use the tool: when you need to list payment prescriptions. However, it does not explicitly state when not to use it or how it compares to the create/update/delete siblings, leaving the agent to infer routing from the verb and sibling names.

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