sherweb_customers_accounts_receivable

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes what data is shown (balances, payment status) but doesn't disclose whether this is a read-only operation, whether it reflects real-time data or cached state, whether it requires specific permissions, what happens if the customer has no outstanding balances, or the format of the response. For a financial data access tool with zero annotation coverage, this is a significant gap.

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 efficient sentence that conveys the purpose and the key data shown. No wasted words. It could be argued that it's slightly under-specified for a financial tool, but as a purpose statement it is appropriately concise and front-loaded.

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?

With no annotations, no output schema, and a financial data retrieval purpose, the description should provide more context about response format, interpretation of the data, or edge cases. The current description tells an agent what data is retrieved but not how to interpret it (e.g., whether 'outstanding balances' are past due, what currency, whether the result is per-invoice or aggregated). For a financial tool targeting accounts receivable, this incomplete context could lead to misuse.

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?

There is only 1 parameter with 100% schema description coverage ('The unique customer ID'), so the schema fully documents the parameter. The description's mention of 'for a specific customer' aligns with the customerId parameter. The description adds no additional syntax or semantic detail beyond what the schema provides, which is acceptable given the high schema coverage of a single straightforward parameter.

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 the verb ('Get') and resource ('accounts receivable information for a specific customer'), and specifies what it shows ('outstanding balances and payment status'). It distinguishes itself from sibling tools like list/get customer tools and billing charge tools by being specific to accounts receivable, though it doesn't explicitly name a sibling to differentiate from.

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 implies this is used to retrieve financial/balance data for a customer, which is clearly distinct from the sibling tools covering customer lists, subscriptions, and billing charges. However, it doesn't explicitly state when to use this versus sherweb_billing_payable_charges or when not to use it, relying on the tool name and purpose to guide selection.

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