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

With no annotations, the description carries the full burden of behavioral disclosure. It conveys an informational, explanatory nature through 'Describe,' implying a read-only operation. However, it does not explicitly state that no side effects occur, nor does it mention the output format or whether it accesses external systems. The output schema exists but is not referenced in the description.

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, focused sentence that immediately states the core purpose. There is no redundant language, and the phrasing is front-loaded with the action verb 'Describe' and the subject 'payments.'

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 zero-parameter explain tool, the description is largely complete: it specifies the exact scope of the explanation (initiation to settlement). It does not explicitly mention Payram, but the sibling tool names and overall context imply this. The output schema covers return-value details, so the description does not need to elaborate further.

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 tool has zero parameters, so the input schema trivially covers all inputs. The description adds no parameter information, but none is needed. Per the guidelines, 0 params results in a baseline score of 4.

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 the specific verb 'Describe' and clearly identifies the resource as 'payment flow' with an explicit scope 'from customer initiation through settlement.' This distinguishes it from sibling explanation tools like explain_referral_flow or explain_payram_concepts, making the purpose unmistakable.

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 no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or situations where another tool (e.g., explain_payram_basics) would be more appropriate. This leaves the agent without decision-support for tool selection.

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