invoices_events

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses what data is returned (a timeline of various event types) but doesn't state whether results are paginated, ordered, filtered, or what the response structure looks like. Since this is a read-only tool, the lack of mutation warnings is less critical, but pagination/ordering behavior would add value.

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 focused sentence that enumerates event types concisely and ends with a use-case sentence. It's lean with no repetition of schema/parameter details. It could arguably be split into two sentences for readability, but it's efficient overall.

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 an audit/history retrieval tool, the description covers the key use cases (audit, debugging, lifecycle understanding) and enumerates the event categories. It doesn't have an output schema, but for a timeline tool the description adequately conveys what will be returned. It doesn't describe pagination or ordering, but this is a simple 2-parameter read tool, so completeness is reasonably high.

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% (uuid and companyId both have descriptions). The description adds meaning by clarifying what the tool does with the invoice and what kinds of events will appear. The schema already explains the companyId override behavior, so the description and schema are complementary. The description's enumeration of event types adds context that helps the agent understand what the uuid refers to.

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 the complete timeline of events for an invoice') and resource (invoice events). It enumerates the event types covered (status changes, ANAF submissions, validations, emails, payments, user actions). It doesn't distinguish from sibling alternatives like invoices_get or efactura_messages_list, but the 'events/timeline' framing is distinct enough among invoice tools.

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 context about when to use ('audit trails, debugging, understanding invoice lifecycle history'), which implies the use case. However, it doesn't explicitly state when NOT to use it or contrast it with alternatives like invoices_get (which returns the current state) or efactura_messages_list (which covers a narrower event subset).

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