Retrieve all unpaid bills in your REG.RU account to review outstanding charges and manage payments. Use it to identify overdue invoices before they affect services.
Get a list of all unpaid bills in the account.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It conveys only scope ('all ... in the account') and nothing about read-only safety, pagination, result caps, or authentication requirements for a billing-related call.
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?
One tight sentence with no filler, and the resource is stated immediately. It is appropriately sized for a parameterless list tool, though it is so short that nothing is front-loaded against anything else.
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, no-output-schema tool this is minimally adequate: the agent knows what it gets. It falls short of complete by omitting whether the list is paginated, sorted, or bounded, which matters for a 'get all' call on bills.
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 takes zero parameters, so the baseline is 4. There is nothing for the description to clarify beyond the account-wide scope, which it already implies.
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 ('Get') and resource ('all unpaid bills in the account'), so the agent knows exactly what it retrieves. It does not differentiate itself from the nearest sibling (regru_get_balance), which also touches billing, but the resource itself is unambiguous.
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?
There is no statement of when to use this tool versus regru_get_balance or any other sibling, and no prerequisites or exclusions. Usage is only weakly implied by the word 'unpaid'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.