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 makes the read-only list behavior clear and adds the precondition that a billing profile attaches to an already-existing contact or company. Still, it does not mention pagination, limits, authentication, or response shape, which an agent may need when invoking a list operation.

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 two sentences with the core action front-loaded in the first sentence. The second sentence explains the resource and adds one clarifying exclusion. There is no redundancy or filler; every sentence earns its place.

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 zero-argument list tool with no annotations and no output schema, the description covers the key essentials: what it lists, its scope, the resource definition, and the contained fields. It falls slightly short on operational details like pagination or response envelope, but for this simple tool the coverage is largely sufficient.

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 input schema has zero parameters, so the baseline for this dimension is 4 and the description is not required to explain parameter behavior. It still adds helpful domain meaning by enumerating the invoicing details each profile contains (currency, payment terms, billing address, tax id), which helps an agent interpret results.

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 opens with 'List every billing profile,' which names a specific verb and resource and clearly marks this as the list-all operation. It distinguishes the tool from billing_profiles_get, billing_profiles_create, and billing_profiles_update by scope and action, and it further clarifies the domain by explaining what a billing profile is and noting there is no separate customers list.

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 provides useful domain context and preemptively tells the agent that no separate customers list exists, which helps prevent a wrong search. However, it never explicitly contrasts this tool with sibling tools like billing_profiles_get or says when to prefer listing all profiles over fetching one. Usage guidance is implied rather than explicit.

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