GET /invoicingMethods (Invoicing Method)

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

Beyond the annotations (readOnlyHint, destructiveHint), the description discloses the dual pagination behavior depending on the limit parameter and its future deprecation. This adds context about operational modes, though it does not detail output structure.

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, efficiently stating purpose, a note on array inputs, and a critical pagination warning. No fluff, front-loaded with key information.

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 no output schema, the description should hint at the return structure (e.g., fields of invoicing methods), but it does not. The pagination warning is helpful but incomplete without specifying the new pagination model details.

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?

With 100% schema description coverage, the tool description adds little new parameter meaning beyond repeating that array-valued parameters accept comma-separated values. The warning about limit is useful but not semantic expansion.

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 is a 'Listagem paginada de Meios de Faturamento' (paginated listing of invoicing methods), using a specific verb and resource. It also differentiates from the sibling 'get_invoicing_method' implicitly through the listing focus.

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 does not provide explicit when-to-use or when-not-to-use guidance compared to siblings. It includes a warning about the limit parameter for pagination but lacks direct comparison with other list or get tools.

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