ghl_invoice_template_update_late_fees_configuration

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

Annotations already indicate a write operation (readOnlyHint=false) with no destructive or idempotent behavior. The description adds the endpoint and version header, but does not disclose additional traits like permissions, side effects, or concurrency. It is adequate but does not go beyond what annotations already imply.

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 concise with three sentences, covering the purpose, endpoint, and source. It could be restructured to front-load key details, but overall it is efficient and not verbose.

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 complexity of nested objects and many sibling invoice-related tools, the description lacks context about the late fees domain, prerequisites, or return values. No output schema exists, and the description does not compensate by explaining what the tool returns or common use cases. It feels incomplete for a configuration update tool.

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 100% with detailed parameter descriptions (e.g., altId, lateFeesConfiguration). The tool description adds no extra meaning beyond the schema, so the baseline score of 3 is appropriate.

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 action ('update') and the resource ('template late fees configuration'). It distinguishes from sibling tools like ghl_invoice_template_update and ghl_invoice_template_update_payment_methods_configuration by specifying the exact configuration aspect being updated. The endpoint details further clarify the scope.

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, such as ghl_invoice_template_update for general template updates. There are no prerequisites, scenarios, or exclusions mentioned. The description only gives the endpoint and version, without contextual usage advice.

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