SubscripitonInvoices_Retrieveas

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only or destructive nature, authentication requirements, rate limits, or pagination behavior. The contradiction between the singular 'retrieve' and list-oriented parameters further obscures behavior.

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 sentence with no unnecessary words. However, it lacks structure and fails to front-load critical information. It is concise but at the expense of completeness.

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?

Given the tool has no annotations, no output schema, and three parameters with pagination and filtering, the description is severely incomplete. An agent cannot determine correct invocation without knowing whether an invoice ID is needed, how pagination works, or what the filter status expects. The context is insufficient for a correct selection or usage.

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?

Schema description coverage is 100% as all three parameters have descriptions, though they are minimal ('Query parameter: ...'). The tool description adds no additional meaning beyond the schema. According to the rubric, high coverage sets baseline at 3, despite the descriptions being sparse.

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 says 'Retrieve a subscription invoice' suggesting a single resource, but the input schema contains pagination and filter parameters (page[size], page[number], filter[status]), which are typical for listing endpoints. This mismatch misleads about the actual function. The sibling 'SubscripitonInvoices_Listallsub' likely handles listing, adding confusion. Purpose is unclear.

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 versus alternatives like 'SubscripitonInvoices_Listallsub' or 'Subscriptions_Retrieveasubscrip'. There is no mention of prerequisites, context, or scenarios where this tool is appropriate.

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