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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly carried structurally. The description adds the useful constraint that save creates only on exactly one of contact/company and that id drives edit vs. delete, but it says nothing about irreversibility of delete, side effects on related invoices, or permission requirements.

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?

Very compact and front-loaded: a one-clause resource definition followed by a per-action breakdown. The telegraphic style ('list (or contactId / companyId for one)') is terse to the point of being clipped, which slightly hurts readability but wastes no space.

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 destructive, 11-parameter, no-output-schema management tool, the description is only minimally sufficient. It covers action semantics and a few fields, but an agent still lacks guidance on destructive delete consequences and on most of the optional payload fields.

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 coverage is 55%, and the description only names four of the eleven fields (currency, terms, billing email, tax id) at a high level. Undocumented-or-thinly-documented fields such as notes, taxExempt, and billingAddress receive no clarification in the description, so it neither compensates for the coverage gap nor adds much beyond the schema.

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 names the resource ('billing details on a contact or company') and enumerates the three operations (list, save, delete) with the fields involved (currency, terms, billing email, tax id). It is clear what the tool does, though it never differentiates itself from nearby siblings like invoice_settings or invoices_manage.

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?

It gives per-action selection guidance: list (optionally scoped by contactId/companyId for a single profile), save (create on exactly one of contact/company, or edit by id), delete. That resolves the main ambiguity for an action-enum tool, though there are no explicit exclusions or pointers to sibling tools.

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