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

The description does disclose the read-only nature, which is a useful behavioral trait. However, with no annotations provided, the description carries the full burden. It does not mention error handling, authentication requirements, rate limits, or what happens if the invoice ID is invalid. For a simple getter, this is minimal but not comprehensive.

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 extremely concise and front-loaded. It communicates the primary function and the read-only guarantee in two short sentences without any extraneous words. This is appropriate for a simple status retrieval tool.

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?

The tool has a single parameter and no output schema, so the description must provide enough context about the return and edge cases. While it mentions the kinds of data returned (status, passes, payment details), it does not describe the response format, error conditions, or any prerequisites. This is insufficient for an agent to know what to expect.

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 schema coverage is 0%, meaning the description does not explain the invoiceId parameter at all. The description omits any mention of the parameter or its purpose. Since there is only one parameter and the description provides zero explanation, it fails to compensate for the lack of schema 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 clearly states it retrieves 'status, remaining passes and payment details for an invoice' and explicitly labels it 'Read-only'. This is specific about the resource and the type of data returned. However, it lacks an explicit verb (e.g., 'get', 'retrieve') and does not directly distinguish it from sibling tools like robyn_plus_invoice or robyn_plus_claim, which might also relate to invoices.

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?

No guidance is provided on when to use this tool instead of alternatives. There is no mention of context, exclusions, or related tools. For example, it doesn't explain how this differs from robyn_plus_invoice or robyn_plus_claim. The description is purely declarative without any usage direction.

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