wafeq_bills_retrieve

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description reinforces this with '🟢 READ-ONLY' and the GET method. It adds the useful scope that exactly one bill is returned, but does not disclose additional behavioral details such as auth requirements, error behavior, or response contents.

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 endpoint and READ-ONLY marker are front-loaded and useful, but 'Retrieve bill' and 'Endpoint for retrieving a single bill' are redundant restatements of the same idea. It is compact, yet a single non-repetitive sentence would be cleaner.

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?

This is a low-complexity read with one required parameter and rich safety annotations, so the basics are covered. However, with no output schema, the description does not indicate what fields or structure the retrieved bill contains, nor what happens for invalid ids, leaving a modest but real gap.

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?

With schema description coverage at 0%, the description carries the burden of explaining the id parameter, but it only echoes /bills/{id}/ and never states id's format, source, or whether it is the Wafeq bill UUID. The schema's 'id: string' plus the URL template is minimal and does not compensate for the missing parameter documentation.

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 clear verb ('retrieving') and a specific resource ('a single bill') and includes the exact endpoint GET /bills/{id}/, so an agent can tell this is the detail fetch for one bill rather than a list operation. It does not explicitly differentiate from wafeq_bills_list or wafeq_bills_line_items_retrieve, but the 'single bill' wording and path do most of the work.

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 phrase 'Endpoint for retrieving a single bill' implies the tool should be used when the agent has a bill id and needs that one bill's details. It gives no explicit when-not-to-use guidance or pointer to alternatives such as wafeq_bills_list for finding bills, so the usage guidance remains implied rather than stated.

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